From nobody Thu May 4 01:56:34 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QBcPK4V6xz49VnV for ; Thu, 4 May 2023 01:56:37 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QBcPK3zdhz4NkG; Thu, 4 May 2023 01:56:37 +0000 (UTC) (envelope-from jbeich@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683165397; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=UpjtfdcN9mzEU72PbEnygiJMG5UXguFAb/OCpMKQ7uQ=; b=QPOXqVt5p1R3UMLjAqeS1Hxnbx5ZkCafsFkI6XUB2bKjn/GTwSgP9xWmr6BnY2Bcsw6x39 h5ZcljfC3AbFXEkK+owp8ji2FbdwRRC95jQtFhMZBSkB0dDRkOPgdJG5DVne3iyovh7PRV CIKaPnaPn90AO/1scFJKiJ4Y3kmfZSoIVOZgclk6/F2ILndRYg//Em+ts0iYK8QwngD7Iz ErvzJwqI2VGXdSd7QILIeOl85Zuv4BvtkzEhBYftNmu1Scoqfk1nfUcEUJWW76GlqYbhc+ Z2TiqcLvvisnAojFj7qXGEHYjoOFU771L9SS7Cfk73yx/vIcLvkZ7fUzeUc7cA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683165397; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=UpjtfdcN9mzEU72PbEnygiJMG5UXguFAb/OCpMKQ7uQ=; b=lS6+6ugCezlM3ix2EgtQW5S99j1yLlMIdP4LLA91aFCVbFFgNq01QfnA/E710NV/uShLGo TGC7uuLMz7SjgAGmQMYioaLCsdOZ1s6gUMUvaEgJjLSg71b32hLcjZu4N/nrf6RodfXpZU B05PVDjTcyI5cqPqrcb8/wsst3yj41I65LvB6sIfbD9zrrEsTViHaiclfhUBg69NbvOw1l hIu6sJSilpNYFO6/yDAHwTXiOhu5v6w49+4IOSAK8GccNFtbpQEl+4K+/1lrfyJPBeTMiX mS/Ve/SkboD7VgB3PmlSmTuFdXfw8nbPdwesNPmjK2BKyTH97Q/cB//hPYrQ+A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1683165397; a=rsa-sha256; cv=none; b=KV5c5zFEl5FfTUNQL54QxcfRTrEPTQO7zs8zohFu6TgLAd9WT0V5vhNkr/sMlk9MdqzlpO bDIRX98ku8GrvhSofxC55Q9UwgTy1G90Gfc/2lEvu4MT0zQXWjlbx1t4H1lNSo9xREyGnu IxH40FffpYRzzfQL/ebKE5Di3faLjWpxZOXuHwc12dqbY9CbUUFiN3/naqIzW6rCemVqnl yOXydyC3VjWaLCy/RKZHKoZydDm8oOjmDLgD0+Arp57gT7CgJwhjedJNSs7PZ9tN9G+piz opYorhubvUPospC5xmL07tX0lKh3oarWvXRZ/ogtjZhhqRvhwIdlgF6Ww82wyA== Received: by freefall.freebsd.org (Postfix, from userid 1354) id 6197A14E3C; Thu, 4 May 2023 01:56:37 +0000 (UTC) From: Jan Beich To: Mark Millard Cc: Current FreeBSD Subject: Re: What llvm16 libc++ updates for -std=c++20 use [was: Re: Delay in 14.0-RELEASE cycle and blocking items] In-Reply-To: (Mark Millard's message of "Wed, 3 May 2023 08:57:08 -0700") References: Date: Thu, 04 May 2023 03:56:34 +0200 Message-ID: <7cto-c10t-wny@FreeBSD.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-ThisMailContainsUnwantedMimeParts: N Mark Millard writes: > Alexey Dokuchaev wrote on > Date: Wed, 03 May 2023 07:53:09 UTC : > >> On Mon, May 01, 2023 at 06:14:49PM +0000, Glen Barber wrote: >> > ... >> > There is no feasible way we are going to make the branch point of >> > stable/14 in time, with that scheduled for May 12, 2023 with the above >> > points. That said, this is not an all-inclusive list, but the more >> > major items on our radar at the moment. >> >> Does this delay mean we might get Clang 16 in the base? Current 15.0.7 >> hits assertion on one of my ports which had allegedly been fixed in 16. >> Also, AFAIU it comes with better support for modern C++, e.g. ranges. > > These notes are based on using -std=c++20 and llvm16 on > opensuse tumblweed (in early April), which has libc++ > support configurable. They also presume that the FreeBSD > llvm16 update fully adopts the libc++ from llvm16. > (FreeBSD LLVM upgrades do not always do so at the initial > upgrade time.) FWIW, std::ranges in base libc++ 16 (via llvm-16-update branch) works fine at least in emulators/yuzu (c++20) and x11-wm/hyprland (c++23). More can take advantage but currently use a workaround e.g., $ rg -l :devel/range-v3 | sed s,/Makefile,, biology/seqan3 devel/fbthrift editors/imhex lang/solidity net-im/telegram-desktop