Date: Sat, 23 Mar 2019 20:52:16 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 207359] head -r339076 TARGET_ARCH=powerpc64 via powerpc64-gcc : some or all c++ exceptions unbounded loop in _Unwind_RaiseException Message-ID: <bug-207359-227-mYpERFtZMN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-207359-227@https.bugs.freebsd.org/bugzilla/> References: <bug-207359-227@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=3D207359 --- Comment #15 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Andrey Rusev from comment #13) Please submit your own defect report. For powerpc64 reverting to FreeBSD 8.4-RELEASE-p35 and gcc 4.2.1 is irrelevant to what I was reporting. powerpc64 does not have the history that amd64 has and a lot has changed since back then. I was reporting an issue explicit tied to giving information for using more modern toolchains than gcc 4.2.1 .=20 For powerpc64, more is now known for what I was reporting and patching efforts to fix both the historical unwind code's DW_CFA_remember_state and DW_CFA_restore_state hnndling and llvm's libunwind's handling of r2 during unwind (the TOC register for powerpc64) are in progress. (It may be that only llvm libunwind will be fixed and used going forward.) --=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-207359-227-mYpERFtZMN>