From owner-freebsd-current@FreeBSD.ORG  Fri Jan 11 07:57:38 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 EB4124F3;
 Fri, 11 Jan 2013 07:57:38 +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 CFEF981B;
 Fri, 11 Jan 2013 07:57:37 +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 <20130111075730.RWWR29828.viefep16-int.chello.at@edge04.upcmail.net>;
 Fri, 11 Jan 2013 08:57:30 +0100
Received: from mole.fafoe.narf.at ([80.109.55.137])
 by edge04.upcmail.net with edge
 id mXxW1k00N2xdvHc04XxWAV; Fri, 11 Jan 2013 08:57:30 +0100
X-SourceIP: 80.109.55.137
Received: by mole.fafoe.narf.at (Postfix, from userid 1001)
 id F2AC16D47C; Fri, 11 Jan 2013 08:57:29 +0100 (CET)
Date: Fri, 11 Jan 2013 08:57:29 +0100
From: Stefan Farfeleder <stefanf@FreeBSD.org>
To: Dimitry Andric <dim@FreeBSD.org>
Subject: Re: clang 3.2 RC2 miscompiles libgcc?
Message-ID: <20130111075729.GA1450@mole.fafoe.narf.at>
References: <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>
 <20130106160331.GB1418@mole.fafoe.narf.at>
 <50EB5868.2050509@FreeBSD.org>
 <20130108085826.GA1422@mole.fafoe.narf.at>
 <50EF5140.60407@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50EF5140.60407@FreeBSD.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: freebsd-current@freebsd.org, David Chisnall <theraven@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: Fri, 11 Jan 2013 07:57:39 -0000

On Fri, Jan 11, 2013 at 12:39:44AM +0100, Dimitry Andric wrote:
> On 2013-01-08 09:58, Stefan Farfeleder wrote:
> > On Tue, Jan 08, 2013 at 12:21:12AM +0100, Dimitry Andric wrote:
> ...
> >> After a lot of splitting up of unwind-dw2.c, I arrived at _Unwind_Resume
> >> which when compiled by clang caused the crashes, but when compiled by
> >> gcc ran OK.
> > your patch seems to work just fine. No crashes whatsoever so far. Thank
> > you.
> 
> I have committed a slighly cleaned-up version of this hack in r245272,
> so until this is fixed by upstream, everybody will at least have a
> correctly functioning libgcc on amd64.
> 
> Since this issue can potentially also occur on stable/9, I will MFC the
> fix too, after a few days timeout.

Thanks!