From owner-freebsd-current@freebsd.org Fri Oct 6 16:05:02 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 54CBFE3A943 for ; Fri, 6 Oct 2017 16:05:02 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-qt0-f172.google.com (mail-qt0-f172.google.com [209.85.216.172]) (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 17757643EF for ; Fri, 6 Oct 2017 16:05:01 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-qt0-f172.google.com with SMTP id 6so23191225qtw.3 for ; Fri, 06 Oct 2017 09:05:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=sq894us461aFht4amgOk6N4elVd3m59E+RB256G823o=; b=Vz9PBoYIo0TG5F1ThcOfkol8h7fdl6dKqBYqXrBwyU19l+5KRzarYWphZo0ht2yDWo 3ztOO1xFs8vgqnhynupty625ATEJfRuMLjUrZG7Pbn3qnA4B95p/rNgMEg+M3ap6T/Af 3fNcAQMVVA3YuiSh5qFSAf7p+Yb7pqV5u34AryJgagnPxXjWgHP2FAkmolc5uypLJsT7 ah5Ko1jiNiics9lBIKeVFySjD6YOHrV1SWlAy7C7iLR1JZ2zJ7LJPxazAZ0PdBm9kUYq w12RdOJITNqWaBPO21kshYHdukff7B4nNboH4upiO1xpUadLsSNf4tVqnKJkFxoxlOzW Jpxg== X-Gm-Message-State: AMCzsaXLI246QZA4XR5QnRZHbsLTR5DbiswjsEz/PUJYS0lmKkIiKybS aLeWXbpWGexLmWM6hMJ3v1UPeANB X-Received: by 10.37.196.65 with SMTP id u62mr1979023ybf.124.1507305894749; Fri, 06 Oct 2017 09:04:54 -0700 (PDT) Received: from mail-it0-f54.google.com (mail-it0-f54.google.com. [209.85.214.54]) by smtp.gmail.com with ESMTPSA id n7sm818176ywh.59.2017.10.06.09.04.54 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Oct 2017 09:04:54 -0700 (PDT) Received: by mail-it0-f54.google.com with SMTP id 72so1777964itl.5 for ; Fri, 06 Oct 2017 09:04:54 -0700 (PDT) X-Google-Smtp-Source: AOwi7QDqqLBGcFhJxnEvSjjWiWk24Vfn0SOPqXnDyW5+FO6vqzCBZ8N6pLr1PCkNfS4+gQlKouzaFivknWSgp/nCohU= X-Received: by 10.36.84.81 with SMTP id t78mr2870129ita.117.1507305894127; Fri, 06 Oct 2017 09:04:54 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.2.144.194 with HTTP; Fri, 6 Oct 2017 09:04:53 -0700 (PDT) In-Reply-To: References: From: Conrad Meyer Date: Fri, 6 Oct 2017 09:04:53 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: C++ in jemalloc To: Mark Millard Cc: Warner Losh , FreeBSD Current Content-Type: text/plain; charset="UTF-8" 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:05:02 -0000 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