Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s6AGF-00ATY1-Mb for pgsql-hackers@arkaria.postgresql.org; Sun, 12 May 2024 14:33:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s6AGC-00BaLa-3f for pgsql-hackers@arkaria.postgresql.org; Sun, 12 May 2024 14:33:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s6AGA-00BaI2-6l for pgsql-hackers@lists.postgresql.org; Sun, 12 May 2024 14:33:08 +0000 Received: from fout5-smtp.messagingengine.com ([103.168.172.148]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s6AG7-000e8W-8v for pgsql-hackers@postgresql.org; Sun, 12 May 2024 14:33:05 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfout.nyi.internal (Postfix) with ESMTP id 71C6B1380358; Sun, 12 May 2024 10:33:01 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Sun, 12 May 2024 10:33:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1715524381; x=1715610781; bh=cqyDn4xebfPhdyYYmhFNcPJkhvHvCv5fvKBfpB3865M=; b= 8aGqz822c5YYnJ2+N9MTrmEH0nKqdPwK4UhOvy94RJHIp9vYw+vZfxpm44Jz7OkC 5Zb30mEmk2qOSuOFZn2sqLa9qV//eOoGKC81Bab5TKOc0Nxxl7m9Kc3gKJrX+/uK pdDGyQkTVEP5+wEl+IfPojolKTk0lLOSqYgPf4lRBJYmWerJod3mtpXkRxLo2LXS H5KZWAcwqogDQ/wxHndTVeUTCdLKCfuJKpcx1i1Xayyquh1wH77PfRseGj/EBowH bcgQ3+jdGGx/T2qME5z2QgjxyhVaX+B6T78FooP0ZVPxl2S9mE6QElNTFd9ou+nW OJxylhYJnQV8Wu8wohl0/A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1715524381; x= 1715610781; bh=cqyDn4xebfPhdyYYmhFNcPJkhvHvCv5fvKBfpB3865M=; b=T VQ0KmzwBZEVpllH99N9gOyX2m3vEcUiCRFjOdF3aLXq7Ul8DfhY90gEZV2XSbww6 AdXbOci2Iqay26I2WEleUm7/0rY9Oy0ZviTAJgl9zKHa0rDQMpMO/AVObW4jHVAz 41uipLz6bY4NQH6ODw9vAB4IqhPE5WMJ0Iz12o/PY6cV//wthR4Yji5wxT+ErvF0 oD+oN196Yill16mnH/PjFNs9syhfW8LPtZcgouo6mSHgLekyYzzse4KQpIPqZo5L uYrlm2QPSalf1ABX3UyycKN7YdSa/CeUv0R4MN4JDijKWcOVLrcPKzQlYqpZ5pXF XCofXANBp5DOzgE9Xqw1g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdegvddgjeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhgqe enucggtffrrghtthgvrhhnpeehiedvhfeuhfeugefgfeehgeejtdevuefhtefhueefvddu gfdtueehgfefudfhffenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 12 May 2024 10:33:00 -0400 (EDT) Message-ID: <5255e75e-5a66-41ac-99d3-1998283b86e6@eisentraut.org> Date: Sun, 12 May 2024 16:32:59 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Requiring LLVM 14+ in PostgreSQL 18 To: Thomas Munro , pgsql-hackers References: Content-Language: en-US From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 24.04.24 01:43, Thomas Munro wrote: > Rebased over ca89db5f. These patches look fine to me. The new cut-off makes sense, and it does save quite a bit of code. We do need to get the Cirrus CI Debian images updated first, as you had already written. As part of this patch, you also sneak in support for LLVM 18 (llvm-config-18, clang-18 in configure). Should this be a separate patch? And as I'm looking up how this was previously handled, I notice that this list of clang-NN versions was last updated equally sneakily as part of your patch to trim off LLVM <10 (820b5af73dc). I wonder if the original intention of that configure code was that maintaining the versioned list above clang-7/llvm-config-7 was not needed, because the unversioning programs could be used, or maybe because pkg-config could be used. It would be nice if we could get rid of having to update that.