From owner-freebsd-current@freebsd.org Fri Oct 6 16:54:43 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 764B0E3BAE6 for ; Fri, 6 Oct 2017 16:54:43 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from cow.apple.relay.mailchannels.net (cow.apple.relay.mailchannels.net [23.83.208.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 352A16615C for ; Fri, 6 Oct 2017 16:54:42 +0000 (UTC) (envelope-from ian@freebsd.org) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id A6C11369155 for ; Fri, 6 Oct 2017 16:17:57 +0000 (UTC) Received: from outbound1a.eu.mailhop.org (unknown [100.96.140.232]) (Authenticated sender: duocircle) by relay.mailchannels.net (Postfix) with ESMTPA id 2742F368FA4 for ; Fri, 6 Oct 2017 16:17:56 +0000 (UTC) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [172.20.110.49]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.14); Fri, 06 Oct 2017 16:17:57 +0000 X-MC-Relay: Forwarding X-MailChannels-SenderId: _forwarded-from|73.78.92.27 X-MailChannels-Auth-Id: duocircle X-Vacuous-Callous: 355dab2c6333e45f_1507306677543_3500172096 X-MC-Loop-Signature: 1507306677543:1363086923 X-MC-Ingress-Time: 1507306677542 X-MHO-User: e49e070c-aab1-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id e49e070c-aab1-11e7-a893-25625093991c; Fri, 06 Oct 2017 16:17:49 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v96GHjpl006240; Fri, 6 Oct 2017 10:17:45 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1507306665.86205.257.camel@freebsd.org> Subject: Re: C++ in jemalloc From: Ian Lepore To: cem@freebsd.org, Mark Millard Cc: Warner Losh , FreeBSD Current Date: Fri, 06 Oct 2017 10:17:45 -0600 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2017 16:54:43 -0000 On Fri, 2017-10-06 at 09:04 -0700, Conrad Meyer wrote: > On Thu, Oct 5, 2017 at 9:58 PM, Mark Millard > 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 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. -- Ian