Date: Fri, 6 Oct 2017 10:04:30 -0700 From: Mark Millard <markmi@dsl-only.net> To: cem@freebsd.org Cc: Ian Lepore <ian@freebsd.org>, Warner Losh <imp@bsdimp.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: C++ in jemalloc Message-ID: <1806F8FF-D0EA-42A2-BA72-85975EAD808F@dsl-only.net> In-Reply-To: <CAG6CVpV4Rs6mSWxTLq=pUi0C0VAKUy0yv42vw4k5E7xkvyPrjQ@mail.gmail.com> References: <BDC9F954-D0C5-4D7A-9CEA-D4FCA595B2FD@dsl-only.net> <CAG6CVpU5Rm87TS=oj_iq_de4POFMiA_NvS8Z_naHb02TnVpOEg@mail.gmail.com> <1507306665.86205.257.camel@freebsd.org> <CAG6CVpV4Rs6mSWxTLq=pUi0C0VAKUy0yv42vw4k5E7xkvyPrjQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1806F8FF-D0EA-42A2-BA72-85975EAD808F>