From owner-freebsd-current@FreeBSD.ORG  Sun Jan  6 16:46:38 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 9A452D3B;
 Sun,  6 Jan 2013 16:46:38 +0000 (UTC)
 (envelope-from theraven@FreeBSD.org)
Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27])
 by mx1.freebsd.org (Postfix) with ESMTP id 4A21D8D0;
 Sun,  6 Jan 2013 16:46:37 +0000 (UTC)
Received: from [192.168.0.2]
 (cpc10-cmbg15-2-0-cust123.5-4.cable.virginmedia.com [86.30.246.124])
 (authenticated bits=0)
 by theravensnest.org (8.14.5/8.14.5) with ESMTP id r06GkTQf033234
 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO);
 Sun, 6 Jan 2013 16:46:30 GMT (envelope-from theraven@FreeBSD.org)
Subject: Re: clang 3.2 RC2 miscompiles libgcc?
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: David Chisnall <theraven@FreeBSD.org>
In-Reply-To: <20130106141708.GA1418@mole.fafoe.narf.at>
Date: Sun, 6 Jan 2013 16:46:27 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA4BC8F5-A501-4E4A-A223-7572B9A65758@FreeBSD.org>
References: <20121227150724.GA1431@mole.fafoe.narf.at>
 <50DC65F5.6060004@freebsd.org> <50E0BD66.4070609@FreeBSD.org>
 <20130102135950.GA1464@mole.fafoe.narf.at>
 <20130104154940.GD1430@mole.fafoe.narf.at>
 <20130106141708.GA1418@mole.fafoe.narf.at>
To: Stefan Farfeleder <stefanf@FreeBSD.org>
X-Mailer: Apple Mail (2.1278)
Cc: freebsd-current@FreeBSD.org, Dimitry Andric <dim@FreeBSD.org>,
 Nathan Whitehorn <nwhitehorn@FreeBSD.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 16:46:38 -0000

On 6 Jan 2013, at 14:17, Stefan Farfeleder wrote:

> On Fri, Jan 04, 2013 at 04:49:41PM +0100, Stefan Farfeleder wrote:
>> Here's a minimal test case that reproduces the bug:
> [...]
>=20
> Until someone fixes this bug, could we apply something like this as a
> work-around?
>=20
> Stefan
>=20
> Index: gnu/lib/libgcc/Makefile
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> --- gnu/lib/libgcc/Makefile	(revision 245055)
> +++ gnu/lib/libgcc/Makefile	(working copy)
> @@ -6,6 +6,8 @@
> SHLIB_NAME=3D	libgcc_s.so.1
> SHLIBDIR?=3D	/lib
>=20
> +CC=3D	gcc
> +
> .include <bsd.own.mk>
> #
> # libgcc is linked in last and thus cannot depend on ssp symbols =
coming

This will break the build entirely for those of us who build without =
gcc, and as we are planning on removing gcc entirely by the 10.0 =
timeframe we should be encouraging people to do this, not discouraging =
it.

Does compiling at a lower optimisation level (-O1?  -O0) work as a =
temporary fix?

David