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 1nK6Vw-0000JH-9C for pgsql-committers@arkaria.postgresql.org; Tue, 15 Feb 2022 22:41:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nK6Vv-0001tD-2u for pgsql-committers@arkaria.postgresql.org; Tue, 15 Feb 2022 22:41:39 +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 1nK6Vt-0001t4-7I for pgsql-committers@lists.postgresql.org; Tue, 15 Feb 2022 22:41:38 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nK6Vo-0000VG-4h for pgsql-committers@lists.postgresql.org; Tue, 15 Feb 2022 22:41:36 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id A1B4932007CF; Tue, 15 Feb 2022 17:41:27 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 15 Feb 2022 17:41:28 -0500 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=fm3; bh=ncO9xw0o615/0SF30jgV1+65A7TYjeHX/c+5tV 6MREs=; b=e47yJC6HaeNmzU0wrI69BinZfM48F5BPA9VMOfWfOHpLzOuujJRimS HZrLIZooXk/oFtTuLhjs00qTBFeFu+ZCGvjZXUwj7ENi1Rs67hbV2TD2GJEmVA4N GGZ4wYcTvAFYyZf1AsPkT9A2pEsRfG2NUJfrDcwNcTTOb38XG8WT4s6sMHlgH5Y2 80meZ3mZkjMqCKyvoVMZoSJwuMjy/m+v1JQqIyzVBTIYnZ+fvkBt5elkvXLFvfhX c7Eu4Uzdbv7ZrQd3XuZ1j6LKtegzNEw1MJzSqImClpOjmd8tD+9aihf1bvhNHVre Ng7AUwxN2U4Mds2Zdc+LFEutOcD9ZPNQ== 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=fm2; bh=ncO9xw0o615/0SF30 jgV1+65A7TYjeHX/c+5tV6MREs=; b=Y+2J3kBxSFpv/27WiZ0I7aaYFdgJBpIy+ KjE69AAWwfcALq2+J4Eh0YhdI+am9W1oHNaEcV4EllqCE23UE3xWjBSOeioqUwKm UCIVeSHgwBnJM4Ltvlz7BljHhkFaVn4bBOr+jEyfDg84scsoGxQXMQqovsD5b54j 7da/3YE2x95cLBXouTa02qOIxPDnewtnOlpOSWOcoizeAV8gmOe0KXYEynZzpnhh QcgqOTOUpPgJSNZVN0M78A9ECDVVCyZu5pscxMfY72gmhkO3COtuH+tp4diQkk0B T9p8+Myg6Mwpbs6SPgh8ClHFfvXdP0fDggRRMEFEOGlbr6XQz2iZQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrjeehucetufdoteggodetrfdotffvucfrrh hofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgenuceurghi lhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurh epfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgurhgvshcuhfhr vghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucggtffrrghtthgvrh hnpefghefgvdehveettefgkeeutdefieefgfduffdtjedtjeetffegffefheekgfelueen ucffohhmrghinheplhhlvhhmrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomheprghnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 15 Feb 2022 17:41:25 -0500 (EST) Date: Tue, 15 Feb 2022 14:41:23 -0800 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: <20220215224123.fx2mxkvlbvhk7377@alap3.anarazel.de> References: <202202142122.eqz4mu2ecfes@alvherre.pgsql> <3155481.1644950069@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-02-16 09:18:53 +1300, Thomas Munro wrote: > Yeah I mentioned this problem in the other thread. I got as far as > finding this write-up: > > https://llvm.org/docs/OpaquePointers.html Given that major parts of llvm (clang alone contains ~1k references) aren't yet transitioned, I wonder if should silence them for now? > I haven't yet tried to work out what we really need to do, but I'm > planning to try. Possibly requires a bit more book keeping on our > part, since eg LLVMGetElementType() is going away. I can't yet really tell whether it'll be simpler because pointer types aren't a thing anymore, or harder because the llvmjit_types.c mechanism won't work well anymore. Greetings, Andres Freund