From owner-freebsd-current@FreeBSD.ORG  Sun Jan  6 16:03:36 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 6884DF9C;
 Sun,  6 Jan 2013 16:03:36 +0000 (UTC)
 (envelope-from stefan@fafoe.narf.at)
Received: from fep16.mx.upcmail.net (fep16.mx.upcmail.net [62.179.121.36])
 by mx1.freebsd.org (Postfix) with ESMTP id 3985B784;
 Sun,  6 Jan 2013 16:03:34 +0000 (UTC)
Received: from edge04.upcmail.net ([192.168.13.239]) by viefep16-int.chello.at
 (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP
 id <20130106160333.MHHL29828.viefep16-int.chello.at@edge04.upcmail.net>;
 Sun, 6 Jan 2013 17:03:33 +0100
Received: from mole.fafoe.narf.at ([80.109.55.137])
 by edge04.upcmail.net with edge
 id kg3Y1k01M2xdvHc04g3Y4V; Sun, 06 Jan 2013 17:03:33 +0100
X-SourceIP: 80.109.55.137
Received: by mole.fafoe.narf.at (Postfix, from userid 1001)
 id 9F0456D449; Sun,  6 Jan 2013 17:03:32 +0100 (CET)
Date: Sun, 6 Jan 2013 17:03:32 +0100
From: Stefan Farfeleder <stefanf@FreeBSD.org>
To: Dimitry Andric <dim@FreeBSD.org>
Subject: Re: clang 3.2 RC2 miscompiles libgcc?
Message-ID: <20130106160331.GB1418@mole.fafoe.narf.at>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50E9916F.3040500@FreeBSD.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: freebsd-current@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:03:36 -0000

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