From nobody Mon Oct 28 20:12:26 2024 X-Original-To: dev-commits-src-main@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 4Xcl181V1Wz5bl4n; Mon, 28 Oct 2024 20:12:28 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xcl1813xGz4BtD; Mon, 28 Oct 2024 20:12:28 +0000 (UTC) (envelope-from dim@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1730146348; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6S5xR6iEnbJvaiMKcPkilNoCRvlabLHCEh4lyb11Vgw=; b=NepbS7pIbGblFMIWvlStaCdIBahM54w3sT1ocxJ5WI5I3BcWhIiqLBN/Zu9r7Pa0izGfFn VFnNysG5LFlGFtJXXYpLHh0UgHFxfDPUO9GbIwzNg3mFgmJHgUIJjsVlPbC8W9KRbxkd02 G1XLkY5Yq+LdRSKNshLPbSerlQL4ocaJ24w3hNMD7hDBsBA7BJTipXvst+7tagkLnRKvOq FRBfqAiQcSRm+YTO3NnsYC8rmINiT6e59J6iz6UXtO7v9p3B8YFnw/knXakxla9Lfel3vZ 2WBEanXnBbGioGzQm+WwLlZEbf6VMFe2SoO757V90k5u8vHLhFVfmzX271d9IQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1730146348; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6S5xR6iEnbJvaiMKcPkilNoCRvlabLHCEh4lyb11Vgw=; b=waBBkpcxCJL8lYjE475ghX6xVm30AwKSqtCmnE/4DzLHjV/VYlKtUUpDCbXhVwd5/Q9xr8 d8saURhKxEEHEWQlqTGlkw5c+oFunZuco4uHvs0BZ8Ahzkb7rXif8E2ydevTYsfk1eIHdW 1bMriwWZ33k3cy+p12c0nh/BL3qp3c/jkWnD9JsDoDNM4M64+kpxjSeFWBF7NCcy2+tNH+ VBR0iOq9pHxkp5uAE7RWRpZddt5d34DKeVvxC1rluxCpRR18w5WvfRQ0MgdKse09/LwbXp IGgTVoo6Y7NerB8W3UiKt7O3Bz+M/IUJaPUyzi2ISDa7f+8BZmUkwmdibCGdvw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1730146348; a=rsa-sha256; cv=none; b=oZjxVFUIlufMtiRhBHWlaeVmU16pZakwjXpiiif0Id/j+DBI9yh2WlCtkLED4S5ZTEcqrW LXIeTsKdr6pn3yU5vBc8LUQZrel0z+yfKBMsbHGw84TMXO46eZPpB34fCivO0PMFAXMz6O 55yoha3cV4zttvH6awpu1HPWWgUNFmeAbs83lr+j7chffaTf09/C1r0XyINkv1D770k454 nXYVFOQRJsp58LfoQDd65sPhcotTegW6zxjR2f7FGHYtS11CX6OWVcg19k55snaImH0YwS 2oDroLgPENQ388ZYQl8km0/Hts9ekwEa5vhRbw5QPVeiE3A+9bBelk5IUefjBw== Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (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 (2048 bits) client-digest SHA256) (Client CN "tensor.andric.com", Issuer "R10" (verified OK)) (Authenticated sender: dim) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Xcl18055fzR8T; Mon, 28 Oct 2024 20:12:27 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from smtpclient.apple (longrow.home.andric.com [192.168.0.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id DAE9C66E41; Mon, 28 Oct 2024 21:12:26 +0100 (CET) Content-Type: text/plain; charset=us-ascii List-Id: Commit messages for the main branch of the src repository List-Archive: https://lists.freebsd.org/archives/dev-commits-src-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: dev-commits-src-main@freebsd.org Sender: owner-dev-commits-src-main@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.2\)) Subject: Re: git: bc9e19dce0ab - main - Fix buildworld with gcc 12 after llvm-19 import From: Dimitry Andric In-Reply-To: <4af71fad-407d-48f2-aec4-f6c50fa72c1f@FreeBSD.org> Date: Mon, 28 Oct 2024 21:12:26 +0100 Cc: "src-committers@freebsd.org" , "dev-commits-src-all@freebsd.org" , "dev-commits-src-main@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <4740E6A9-B104-46C5-AB19-9C5F2BF66AA3@FreeBSD.org> References: <202410251608.49PG8pSI044793@gitrepo.freebsd.org> <4af71fad-407d-48f2-aec4-f6c50fa72c1f@FreeBSD.org> To: John Baldwin X-Mailer: Apple Mail (2.3731.700.6.1.2) On 28 Oct 2024, at 20:56, John Baldwin wrote: >=20 > On 10/25/24 12:08, Dimitry Andric wrote: >> The branch main has been updated by dim: >> URL: = https://cgit.FreeBSD.org/src/commit/?id=3Dbc9e19dce0abee80750e6fa04aaf9798= 73bfe0d2 >> commit bc9e19dce0abee80750e6fa04aaf979873bfe0d2 >> Author: Dimitry Andric >> AuthorDate: 2024-10-25 16:07:59 +0000 >> Commit: Dimitry Andric >> CommitDate: 2024-10-25 16:08:32 +0000 >> Fix buildworld with gcc 12 after llvm-19 import >> Unfortunately gcc 12's is not yet capable of compiling all = of libc++ >> 19's C++23 code, which results in errors similar to: >> = /usr/src/freebsd/src/contrib/llvm-project/libcxx/include/__algorithm/range= s_contains.h:41:3: error: 'static constexpr bool = std::__1::ranges::__contains::__fn::operator()(_Iter, _Sent, const = _Type&, _Proj)' must be a non-static member function >> 41 | operator()(_Iter __first, _Sent __last, const _Type& = __value, _Proj __proj =3D {}) { >> | ^~~~~~~~ >> = /usr/src/freebsd/src/contrib/llvm-project/libcxx/include/__algorithm/range= s_contains.h:48:3: error: 'static constexpr bool = std::__1::ranges::__contains::__fn::operator()(_Range&&, const _Type&, = _Proj)' must be a non-static member function >> 48 | operator()(_Range&& __range, const _Type& __value, = _Proj __proj =3D {}) { >> | ^~~~~~~~ >> Until we can get rid of gcc 12, work around this by making = it compile >> libc++ in C++20 mode instead. >> NOTE: The resulting libc++ library will not be C++23 = compatible! Please >> try to avoid shipping it, and use gcc 13 instead, if you must use = gcc. >> PR: 280562 >> MFC after: 3 days >=20 > In this case I think we probably should drop support for GCC 12 for = main. Just let me > know when you are thinking of merging libcxx 19 to stable branches so = I can ensure they > build with GCC 13/14 and get our CI jobs updated before then. It depends a bit on how many ports still need to be fixed, and of course = when 13.5 and 14.2 are done. After those I will probably do the merges. That said, is gcc 13 good for all arches we want to support? In the past = we still kept a few old gcc versions alive because they were the only = one that could build for $OBSOLETE_ARCH. -Dimitry