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 1qv3zi-002vEJ-FQ for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Oct 2023 23:05:58 +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 1qv3zg-00Gmzb-77 for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Oct 2023 23:05:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qv3zf-00Gmyb-T8 for pgsql-hackers@lists.postgresql.org; Mon, 23 Oct 2023 23:05:56 +0000 Received: from mail-pf1-x42b.google.com ([2607:f8b0:4864:20::42b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qv3zZ-002MM1-KH for pgsql-hackers@lists.postgresql.org; Mon, 23 Oct 2023 23:05:56 +0000 Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-6b7f0170d7bso3677547b3a.2 for ; Mon, 23 Oct 2023 16:05:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698102347; x=1698707147; darn=lists.postgresql.org; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=37iJYhtqVT0DUExJhcllzjLVIVyx1HkgDplJ9UVtJjA=; b=I+30WNiRLZHlgRbPloHmUGs7GmDva4NG/m+hg+9dF+vDK6CcD2xFSqwslg32GWQ3Lk wzPhXVADh+sgaW5FL+sw1RFBAQFc1zkAWkSrzjvxKhX1cq3V7UcstG0/RE4T8Ug60tJj B9DzsHGNrd//mjXvDu316/9LCZmPtShoJBvAoQj3o6XcgG6SsFwHZEn+oNGRQJY4C9oq iNTOwB/xu/Y3ltaTrDhHZwepV6X0yLhaCL9v2tFACKwFKxghlHaF+Qp0n6f5Ya0W30n1 Fo3tgtWuod8GDdJDR51GBa5HHBXOe1ebrMflA/AiU6XzZ9sUcFn9auXO/Zoyhnecp1Pn vE7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698102347; x=1698707147; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=37iJYhtqVT0DUExJhcllzjLVIVyx1HkgDplJ9UVtJjA=; b=d3zY+ynCkXu3GA9c2hL7K8QH1kAqe1pbnEttwwUkj/Zqoen3VK5w45QVWY0tCaVatB wPnvXQuU0YnxwtlUVXWQnBNpTPjmdY18uh/Qku8Aj7+6OLgArsZiqInimZhs5jE1d7PB 2rqL+lq0/Os2begwog55g3TNUB59A0Ll0y0WawVztA4OMv+FM7D9n0WzV+2UrsAZg2Zr ga/yIPp8Ye1bvWiTDhCZ2SJxgnx89EmxPpqM/CAznM1q7sMPPIY6M04rGFj1+AOJRY2h u4YGieLAOVSH4+m9yscdPo4QhwBNfJBwYydbTsEA355beBNT7vq1LzbRFeF2rX/XTxrC yOBQ== X-Gm-Message-State: AOJu0Yw7RB7Xe9JQPjpK6V+2lk84Io2GolAQI/xgAC1Y9NmI5PemqSG7 U3ImedJlvtqdQag0BeyjHVE= X-Google-Smtp-Source: AGHT+IGrd7+jXjq8tZE3wdj07NRXdxuFY2kExjSn53PpIqN+OrDGwtzikMGpAs6pETfhM9ElStEwJQ== X-Received: by 2002:a05:6a00:987:b0:6be:1f19:e604 with SMTP id u7-20020a056a00098700b006be1f19e604mr13618579pfg.21.1698102347379; Mon, 23 Oct 2023 16:05:47 -0700 (PDT) Received: from moubin (71-36-110-102.ptld.qwest.net. [71.36.110.102]) by smtp.gmail.com with ESMTPSA id z11-20020aa79e4b000000b006b725b2158bsm6686580pfq.41.2023.10.23.16.05.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 23 Oct 2023 16:05:46 -0700 (PDT) Date: Mon, 23 Oct 2023 16:05:44 -0700 From: Mark Wong To: Thomas Munro Cc: Tom Lane , Ronan Dunklau , Devrim =?iso-8859-1?B?R/xuZPx6?= , PostgreSQL Hackers , Fabien COELHO , Dmitry Dolgov <9erthalion6@gmail.com>, Andres Freund Subject: Re: LLVM 16 (opaque pointers) Message-ID: References: <20231020221213.zlgwsh7wtwyz33ag@awork3.anarazel.de> <4022690.1697852728@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Oct 24, 2023 at 10:17:22AM +1300, Thomas Munro wrote: > On Tue, Oct 24, 2023 at 4:27 AM Mark Wong wrote: > > I haven't gotten around to disabling llvm on any of my animals with llvm > > < 7 yet. Do you still want to hold on that? > > Yes, please disable --with-llvm on s390x and POWER animals with LLVM < > 7 (see below). Also, you have a bunch of machines with LLVM 16 that > are failing to compile on REL_11_STABLE. That is expected, because we > agreed not to back-patch the LLVM 16 API changes into REL_11_STABLE: > > > kingsnake: 16.0.6 Fedora Linux 38 > > krait: CentOS 16.0.6 Stream 8 > > lancehead: CentOS 16.0.6 Stream 8 I should have updated these to not use --with-llvm for REL_11_STABLE. > These POWER machines fail as expected, and it's unfixable: > > > elasmobranch: 5.0.1 openSUSE Leap 15.0 > > demoiselle: 5.0.1 openSUSE Leap 15.0 > > cavefish: 6.0.0 Ubuntu 18.04.6 LTS These should now be updated to not use --with-llvm at all. > These s390x animals are failing, but don't show the layout complaint. > I can see that LLVM 6 also lacked a case for s390x in > llvm::orc::createLocalIndirectStubsManagerBuilder(), the thing that > was fixed in 7 with the addition of a default case. Therefore these > presumably fail just like old LLVM on POWER, and it's unfixable. So I > suggest turning off --with-llvm on these two: > > > cotinga: 6.0.0 Ubuntu 18.04.6 LTS > > perch: 6.0.0 Ubuntu 18.04.6 LTS Ok, I should have removed --with-llvm here too. > This s390x animal doesn't actually have --with-llvm enabled so it > passes, but surely it'd be just like lora: > > > mamushi: 15.0.7 Red Hat Enterprise Linux 9.2 Oops, I think I added it now. I think I made all the recommended changes, and trimmed out the lines where I didn't need to do anything. :) Andres pointed out to me that my animals aren't set up to collect core file so I'm also trying to update that too... Regards, Mark