From owner-freebsd-current@FreeBSD.ORG Tue Jan 8 08:08:21 2013 Return-Path: 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 C633015F; Tue, 8 Jan 2013 08:08:21 +0000 (UTC) (envelope-from theraven@freebsd.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id 98337D5; Tue, 8 Jan 2013 08:08:20 +0000 (UTC) Received: from [192.168.0.2] (cpc10-cmbg15-2-0-cust123.5-4.cable.virginmedia.com [86.30.246.124]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r0888Chf042159 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Tue, 8 Jan 2013 08:08:13 GMT (envelope-from theraven@freebsd.org) Subject: Re: clang 3.2 RC2 miscompiles libgcc? Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: David Chisnall In-Reply-To: <50EB5868.2050509@FreeBSD.org> Date: Tue, 8 Jan 2013 08:08:08 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <1D415F08-5FFC-41B5-9A0D-E03757800E0C@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> <20130106160331.GB1418@mole.fafoe.narf.at> <50EB5868.2050509@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.1278) Cc: Stefan Farfeleder , Nathan Whitehorn , freebsd-current@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2013 08:08:21 -0000 On 7 Jan 2013, at 23:21, Dimitry Andric wrote: > This is at least the direction I'm looking at. It seems that in some > cases with __builtin_eh_return(), llvm does not see that registers can > be clobbered, and it doesn't save and restore them. Do you mean that some registers were clobbered by a prior call? = __builtin_eh_return() doesn't return, so whether it clobbers anything or = not isn't something that should matter. The preceding call is = __builtin_frob_return_addr, which seems to be a no-op, so it shouldn't = clobber any registers either... David=