Date: Fri, 6 Oct 2017 09:04:53 -0700 From: Conrad Meyer <cem@freebsd.org> To: Mark Millard <markmi@dsl-only.net> Cc: Warner Losh <imp@bsdimp.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: C++ in jemalloc Message-ID: <CAG6CVpU5Rm87TS=oj_iq_de4POFMiA_NvS8Z_naHb02TnVpOEg@mail.gmail.com> In-Reply-To: <BDC9F954-D0C5-4D7A-9CEA-D4FCA595B2FD@dsl-only.net> References: <BDC9F954-D0C5-4D7A-9CEA-D4FCA595B2FD@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 5, 2017 at 9:58 PM, Mark Millard <markmi@dsl-only.net> wrote: > Luckily most kernel and world code that I actively use > does not throw C++ exceptions in my use. > > But devel/kyua is majorly broken by the C++ exception > issue: It makes extensive use of C++ exceptions. In my > view that disqualifies clang as being "close": I view > my activity as a hack until devel/kyua is generally > operable and so available for use in testing. I don't think that is a major roadblock; a broken port is a broken port. Kyua is a relatively unimportant one for most users. In this particular case, maybe kyua (a leaf binary) could be built with GCC instead of Clang on any platform with broken C++ exceptions. Best, Conrad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpU5Rm87TS=oj_iq_de4POFMiA_NvS8Z_naHb02TnVpOEg>