On 2017-Oct-6, at 9:58 AM, Conrad Meyer <cem at freebsd.org> wrote:

> On Fri, Oct 6, 2017 at 9:17 AM, Ian Lepore <ian at freebsd.org> wrote:
>> It isn't about "a broken port".  All C++ code is broken if exceptions
>> don't work.  That means devd is broken.  Not to mention clang itself.
>> It may be that neither of those relies on exceptions for routine
>> operation and uses them only for error handling, and errors mostly
>> don't happen.  There is plenty of C++ code in the world where
>> exceptions are used in non-fatal-error cases and where the applications
>> just don't work at all without them.
> Then use G++ for C++ on those second-tier architectures.  We've got a
> working C++ toolchain.

g++'s toolchain (such as via devel/powerpc64-xtoolchain-gcc )
has its own problems:

A) For targeting powerpc64 it fails to build a working lib32.
   (This may well be better than clang's status overall.)

B) For targeting powerpc (32-bit): what toolchain?

Mark Millard
markmi at dsl-only.net

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to