Date: Fri, 11 Jan 2013 00:39:44 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Stefan Farfeleder <stefanf@FreeBSD.org> Cc: freebsd-current@freebsd.org, David Chisnall <theraven@freebsd.org>, Nathan Whitehorn <nwhitehorn@freebsd.org> Subject: Re: clang 3.2 RC2 miscompiles libgcc? Message-ID: <50EF5140.60407@FreeBSD.org> In-Reply-To: <20130108085826.GA1422@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> <20130106160331.GB1418@mole.fafoe.narf.at> <50EB5868.2050509@FreeBSD.org> <20130108085826.GA1422@mole.fafoe.narf.at>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50EF5140.60407>