Date: Sat, 23 Mar 2019 20:43:08 +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-nhfXul2cuH@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 #14 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Andrey Rusev from comment #12) My original submittal did not involve "unknown pointer encoding". What you report for amd64 is not similar at all. (Modern amd64 uses llvm libunwind, not the historical unwind code.) Please submit your own defect report for your context. Things have progressed, in that for lbgcc_s.so historical unwind code I now run with a patch that completes the implementation of DW_CFA_remember_state and DW_CFA_restore_state. building via devel/powerpc64-xtoolchain-gcc materials ( such as devel./powerpc64-gcc ) works for C++ exception handling. There is a patch under review for llvm materials to fix llvm's libunwind for pwoerpc64 code so that it correctly handles the r2 (TOC) register, at least for the code models normally used. --=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-nhfXul2cuH>