From owner-freebsd-current@FreeBSD.ORG Wed Jan 2 13:59:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7AAC31C; Wed, 2 Jan 2013 13:59:55 +0000 (UTC) (envelope-from stefan@fafoe.narf.at) Received: from fep11.mx.upcmail.net (fep11.mx.upcmail.net [62.179.121.31]) by mx1.freebsd.org (Postfix) with ESMTP id A7DA28FC12; Wed, 2 Jan 2013 13:59:53 +0000 (UTC) Received: from edge04.upcmail.net ([192.168.13.239]) by viefep11-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20130102135952.STYZ2060.viefep11-int.chello.at@edge04.upcmail.net>; Wed, 2 Jan 2013 14:59:52 +0100 Received: from mole.fafoe.narf.at ([80.109.55.137]) by edge04.upcmail.net with edge id j1zs1k00T2xdvHc041zsEq; Wed, 02 Jan 2013 14:59:52 +0100 X-SourceIP: 80.109.55.137 Received: by mole.fafoe.narf.at (Postfix, from userid 1001) id F3B036D454; Wed, 2 Jan 2013 14:59:50 +0100 (CET) Date: Wed, 2 Jan 2013 14:59:50 +0100 From: Stefan Farfeleder To: Dimitry Andric Subject: Re: clang 3.2 RC2 miscompiles libgcc? Message-ID: <20130102135950.GA1464@mole.fafoe.narf.at> References: <20121227150724.GA1431@mole.fafoe.narf.at> <50DC65F5.6060004@freebsd.org> <50E0BD66.4070609@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50E0BD66.4070609@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org, Nathan Whitehorn X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2013 13:59:55 -0000 On Sun, Dec 30, 2012 at 11:17:10PM +0100, Dimitry Andric wrote: > > I have been playing with Stefan's testcase for a while now, and while I > can reproduce the crashes, I am still at a loss about the cause. It > does seem to have something to do with throwing exceptions, but I am > still not sure whether I am looking at a bug in boost, gcc, clang, or > libgcc... > > Do you happen to have a smaller testcase, by any chance? Not yet, but I'll try to come up with something smaller. Stefan