From owner-freebsd-current@freebsd.org Fri Oct 6 16:29:10 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 A40C5E3B10F for ; Fri, 6 Oct 2017 16:29:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 67CFB6512E for ; Fri, 6 Oct 2017 16:29:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22d.google.com with SMTP id y15so1778771ita.4 for ; Fri, 06 Oct 2017 09:29:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=c3xOeWv6zcYAloNfAD7zWUBQg51VxYHdSxHsG0DeRGA=; b=f7JR8E+vWot2Z1VwCYUQOnsj1OVqUinsUo8p9C1ELIIHp3LaebAjPoGBY30QmnYKT3 pYmMPzFsijOkFu+5dIZin/1e9tR28jXMRbHRNP7YDWYe0cH6Hd44llP/lD3SlvvPH0Ac aOiuG4y/lUV6zjJIp96ElVP5kNXD7sWPioovT4gM62gdSOl3Ovj8lEDU7PtVJUPkT5JI 2xzUUEqyy/7aWbx3Z7zcFHqLejAOyK7qFSOFrPaVv/uLc7TFzzqQQT4gZ9c+YliVVTPz 56WLJR5p8oyBSusWx4KbBWDE7hOqrQZXMk6y32Hdyd7K31Itu0FuxzwDKMs1OQ5brBlC ffoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=c3xOeWv6zcYAloNfAD7zWUBQg51VxYHdSxHsG0DeRGA=; b=VV4vTG6k5o0yE5XNBdBPVAL/IIQJTN3adJsxokUASnxvFo5ZqBOdDh4mBQs+4A4HQP KYyaKib040E2YoLXIyVYZof1SfV+Go2suwgsuozRl7bnnBg0w2haHDXvIJ3cXUUVIjeB cvU8lsgWcRwfqCwRC4oNN/movuawHT17by8ExSTIY4O+l3FnAxXtWdp3i2tRH4ULvfKm YLH6b42bk/1LE2729VTcWHJ1/OGL/maoOrhh9V555TBGaogrG8BJFH9c7AEC/PZvpmBv xzNZuPHdn8w3hgCmD2ELlrBpyBuH7iFSuX/NPRonRAjOkL+77EDVZ0eMtfQrr8PRwYxt I68g== X-Gm-Message-State: AMCzsaVtozRPXpk/pvSwPPTC2LuoHDNvspud2J2sGzx2Z1QBBpgEal8b kYkL2AUrxMGZU+gVytrYTHHMneJhJfgEBiIMBcJI4Q== X-Google-Smtp-Source: AOwi7QDcaRNONp2C+jX79Ra9kmNxt3vEkiabTwOe+Vy6p0A25nubkC8pZwf+9K/F+07Lz5DfMptSs7TdwMOI/6kEkkA= X-Received: by 10.36.19.207 with SMTP id 198mr3003936itz.130.1507307348386; Fri, 06 Oct 2017 09:29:08 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.94.130 with HTTP; Fri, 6 Oct 2017 09:29:07 -0700 (PDT) X-Originating-IP: [192.173.66.161] In-Reply-To: <1507306665.86205.257.camel@freebsd.org> References: <1507306665.86205.257.camel@freebsd.org> From: Warner Losh Date: Fri, 6 Oct 2017 09:29:07 -0700 X-Google-Sender-Auth: T3F0oR-kWvaPGbhD3hOm_UOPDzM Message-ID: Subject: Re: C++ in jemalloc To: Ian Lepore Cc: "Conrad E. Meyer" , Mark Millard , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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:29:10 -0000 On Fri, Oct 6, 2017 at 9:17 AM, Ian Lepore wrote: > 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. > I'm with Ian: Broken C++ exceptions means a broken C++ compiler. It's best to think of it like the tertiary operator being wonky in 'C'... Warner