From owner-freebsd-bugs@freebsd.org  Sun Mar  6 08:13:58 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F4A39DA249
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sun,  6 Mar 2016 08:13:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2FE3F219
 for <freebsd-bugs@FreeBSD.org>; Sun,  6 Mar 2016 08:13:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u268Dwiu034726
 for <freebsd-bugs@FreeBSD.org>; Sun, 6 Mar 2016 08:13:58 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 207732] libgcc_s .eh_frame handling messes up interpreting
 powerpc/powerpc64 frame pointer register use produced by clang 3.8.0
Date: Sun, 06 Mar 2016 08:13:58 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: markmi@dsl-only.net
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Not A Bug
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: resolution bug_status
Message-ID: <bug-207732-8-6DMZ9RMnPO@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207732-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-207732-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Mar 2016 08:13:58 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207732

Mark Millard <markmi@dsl-only.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |Not A Bug
             Status|New                         |Closed

--- Comment #2 from Mark Millard <markmi@dsl-only.net> ---
With the other errors identified and reported for .eh_frame and C++ excepti=
on
handling for powerpc it is getting harder to tell if a problem is a new pro=
blem
or a consequence of the other ones. (Various problems have no work around y=
et
to avoid them.)

This turned out to be a consequence of the other problems.

It was easier to discover once I induced gcc 4.2.1 to generate some example
code with r31 in use as a frame pointer. (I used alloca.) Observing its
behavior and the .eh_frame output indicated I'd misinterpreted where the
earliest problem was.

--=20
You are receiving this mail because:
You are the assignee for the bug.=