Date: Mon, 27 Mar 2017 20:13:28 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 218125] compiler:c++11-lib feature should choose gcc5+ or clang3x for powerpc64 Message-ID: <bug-218125-13-H68juvaapC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218125-13@https.bugs.freebsd.org/bugzilla/> References: <bug-218125-13@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=3D218125 Mark Millard <markmi@dsl-only.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markmi@dsl-only.net --- Comment #1 from Mark Millard <markmi@dsl-only.net> --- clang (even 4.0) does not work for TARGET_ARCH=3Dpowerpc : It has basic problems with stack handling for R30 use when floating point is involved for the ABI that FreeBSD uses. Also the handing of thrown C++ exceptions is messed up. clang (even 4.0) does not work for TARGET_ARCH-powrepc64 : The handling of thrown C++ exceptions is messed up. There are llvm bugzilla submittals for such things and they are on the llvm bugzilla meta- entry for what blocks use by FreeBSD as the system compiler. Note: clang 3.x was in worse shape until 3.9.x . clang is a long way from being able to be the compiler for the likes of kyua for QA testing FreeBSD. So I believe that any "or clang" is a bad idea still. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218125-13-H68juvaapC>