Date: Sat, 18 Mar 2017 22:11:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 178038] clang++ fails to produce a binary in powerpc64 Message-ID: <bug-178038-21-3wDzJEZZRg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-178038-21@https.bugs.freebsd.org/bugzilla/> References: <bug-178038-21@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=3D178038 Mark Millard <markmi@dsl-only.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markmi@dsl-only.net --- Comment #3 from Mark Millard <markmi@dsl-only.net> --- [This is not an objection to closing 178038. It is more of a status note since while kyua builds it does not work.] I've built kyua via system clang 3.8 and later for powerpc family members. The builds completed. But even as of clang 4.0 the code generation is bad and kyua fails to run. This is for both TARGET_ARCH=3Dpowerpc64 and TARGET_ARCH=3Dpowerpc. All of the below applies to clang 4.0 (so far). kyua makes extensive use of C++ exception handling, among other things. One problem for both TARGET_ARCH's is that handling thrown C++ exceptions is messed up. Even: #include <exception> int main(void) { try { throw std::exception(); } catch (std::exception& e) {} return 0; } fails. This makes kyua currently useless. TARGET_ARCH=3Dpowerpc also has problems with use and restore of R31 when floating point code is involved (restored for returning but later used for floating point code expecting R31 to not have been restored yet). (There may be more issues for one or both TARGET_ARCH's but the above is sufficient to classify clang as broken for kyua.) --=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-178038-21-3wDzJEZZRg>