Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nUBv0-00069T-DY for pgsql-committers@arkaria.postgresql.org; Tue, 15 Mar 2022 18:29:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nUBuy-0002VH-4I for pgsql-committers@arkaria.postgresql.org; Tue, 15 Mar 2022 18:29:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nUBuw-0002V8-Fz for pgsql-committers@lists.postgresql.org; Tue, 15 Mar 2022 18:29:11 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nUBuo-0008Is-Kj for pgsql-committers@lists.postgresql.org; Tue, 15 Mar 2022 18:29:10 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 7B01E5C0250; Tue, 15 Mar 2022 14:29:00 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 15 Mar 2022 14:29:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=sN3XK0umElT9I+aTe2qyTjRS0w1RuFgK9THsLG bAxkk=; b=SCHi99aEtqbQvuFt9jVgcU9QltfjVHKCmaExLrzj3qIwcRzq1YdiNJ YvGRLTLJVCCeqohmG9SQIWC0v5KsFpqhSAh9KGXG/q9zD51onm8bWpR7/cgcvEK6 CCELqJHPoYtkHXeA/BK9xOQmyHicLMyi+AnZu4D5DN+SvlN8Jq5bGa5uwHo1n616 e3PuqJxNb9867eeaj3UsngjImHxGZ1R0fBYpP2UsUyC4VXqrAMn5w7E4FHnkHuoI Xtdd/3QhsJZc/865LmWrJougGeaIpAqmSGLnke1kS1bfKwp8/rzpUcUA0BVGrAYq uM3ichJfHYp7fpUmRWYGFAtTwcUanqrA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=sN3XK0umElT9I+aTe 2qyTjRS0w1RuFgK9THsLGbAxkk=; b=j42/nWb2FvTQtddiCMLusXKD0HWPWAWph 4HLUOitGfGR4H0UoaCvFH14/E2ceZsLS+ECs0tvGs/tjC/exR7hUb7gcXoEjHV2I Q5TzIdwyxaPW1h10g7Lh+ZM5zHhevHCDXQoA/dNm+W+hVca7XM8lvZiMyoVWcWKB 9msmXNsmQeJ9fCS1EjfncMrPWToQCbSWC3PC809jclS26WLrAmF7jvtahXDOZixp 4cxa3+TGnjYjhIuaQmRfPbNZX9/I1iVL0wD6kty4jBv8tIyivJiLUbT4WTc3g70N XZRh4E53ULLIXC8XbqbPfPP6B2iJVv6hvtNoXTWXJbw31LucSiBtg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudeftddgudduvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomheptehnughr vghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecuggftrf grthhtvghrnhepudekhfekleeugeevteehleffffejgeelueduleeffeeutdelffeujeff hfeuffdunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh eprghnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 15 Mar 2022 14:28:59 -0400 (EDT) Date: Tue, 15 Mar 2022 11:28:58 -0700 From: Andres Freund To: Thomas Munro Cc: Tom Lane , Alvaro Herrera , Fabien COELHO , Thomas Munro , pgsql-committers Subject: Re: pgsql: Track LLVM 15 changes. Message-ID: <20220315182858.dm4vc6q2ucfctcyf@alap3.anarazel.de> References: <202202142122.eqz4mu2ecfes@alvherre.pgsql> <3155481.1644950069@sss.pgh.pa.us> <20220215224123.fx2mxkvlbvhk7377@alap3.anarazel.de> <3224284.1644965080@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2022-03-15 12:12:44 +1300, Thomas Munro wrote: > Shortly I'll do the back-patch of LLVM 14 API changes (their final > release tag is scheduled for tomorrow, as I've been reminded by > package maintainers trying and failing to build). +1 > But I figured I > should also follow up on this bandaid solution to the API deprecation > warnings, that is, silencing them for now, so we don't spew screeds of > warnings. Does someone have a better idea than the attached? Hm. No, no I don't see something better. There's ugly stuff like redefining LLVM_ATTRIBUTE_DEPRECATED but that seems worse. Greetings, Andres Freund