Date: Sun, 6 Jan 2013 17:03:32 +0100 From: Stefan Farfeleder <stefanf@FreeBSD.org> To: Dimitry Andric <dim@FreeBSD.org> Cc: freebsd-current@freebsd.org, Nathan Whitehorn <nwhitehorn@freebsd.org> Subject: Re: clang 3.2 RC2 miscompiles libgcc? Message-ID: <20130106160331.GB1418@mole.fafoe.narf.at> In-Reply-To: <50E9916F.3040500@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> <50E9916F.3040500@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 06, 2013 at 03:59:59PM +0100, Dimitry Andric wrote: > On 2013-01-06 15: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: > > [...] > > > > Until someone fixes this bug, could we apply something like this as a > > work-around? > > > > Stefan > > > > Index: gnu/lib/libgcc/Makefile > > =================================================================== > > --- gnu/lib/libgcc/Makefile (revision 245055) > > +++ gnu/lib/libgcc/Makefile (working copy) > > @@ -6,6 +6,8 @@ > > SHLIB_NAME= libgcc_s.so.1 > > SHLIBDIR?= /lib > > > > +CC= gcc > > + > > .include <bsd.own.mk> > > I think this is a bit overkill approach. We still don't know what the > exact cause of the problem is, and this just papers over it. It seems unwise to install a known-to-be-broken libgcc by default, even though the exact cause is not known yet. > Also, ince the bug is only reproducible by compiling the testcase with > g++, could you not compile your crashing programs with clang instead, > for now? :-) The bug also affects ports software, e.g., I also experienced strange rtorrent segfaults that are now gone. Stefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130106160331.GB1418>