Date: Sun, 06 Mar 2016 08:13:58 +0000 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 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-207732-8-6DMZ9RMnPO>