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 1qtxY4-00FDhO-Le for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Oct 2023 22:00:52 +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 1qtxY1-008EXA-Qy for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Oct 2023 22:00:50 +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 1qtxY1-008EX2-HK for pgsql-hackers@lists.postgresql.org; Fri, 20 Oct 2023 22:00:50 +0000 Received: from mail-il1-x135.google.com ([2607:f8b0:4864:20::135]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qtxXx-001nO6-Rk for pgsql-hackers@lists.postgresql.org; Fri, 20 Oct 2023 22:00:49 +0000 Received: by mail-il1-x135.google.com with SMTP id e9e14a558f8ab-351574aca7bso4734165ab.3 for ; Fri, 20 Oct 2023 15:00:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697839244; x=1698444044; 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=heIBcvIDMTFGOMsqfGaJoo87mXbz911/zzUB5glyJPI=; b=AnqZwecovuxXvK72wUmXM2UCeztgTAI9mze3Ol88SFCRZqLOlwE5OQrWUuTdj8Soy7 WKB30jfrz/T1pz20Vj0osv0q71eZRx2yBpd8elnr/N8PnnMilYUjIreCX4SNAsgkFd4C 4v0NiqOuAvyfTOGWMSvFFzKfG3ejjcA9F9UBvoL/y3buapxnRWBVM3Hptahd9kMLkWwS Z1bbYJTrIM/zSc2h0DPCxKBqz22MwL8dGXmSSO4ymYRYvuYII30mCn1rm5QKFwIIfcng BNx2xjdwWQ5z7mvzz8rcsn3TyNBOA/YyVy16kLoxMIFQlBB2VgrKGfmOyRxvMA5u1Ma+ rvkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697839244; x=1698444044; 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=heIBcvIDMTFGOMsqfGaJoo87mXbz911/zzUB5glyJPI=; b=FqOt6ThEBpmgIU53hyq5v2euADPnHPp4dujrfkEYO5TkX2PSMR1BkAiNhnYbapGCSr zl49DYxfr6lY8GOv2YA/OiRilxjK5xfh8SGI91MZq61e++fZQUXIYBfSNJ4yaEUiLtKq GEUM4mt1ND0HteQtNtnLBh+7/AVjN5nXpbeNUctF1njmyjJF13ppA0MIbEzbQLmxkvcV 963i5DHwvB9g/76ZDIrnP+neh1Tfentb0GFJhj55+ug8x/lRSMBwpDp4jzhzTlGe2/RT irOiZivurN4r+z1A9cOkKejAitKPu69vyXJme0IIDiVASLDyZewtTI/GH5FaV2GryHas P24A== X-Gm-Message-State: AOJu0YxkGPR/9Ea9tOaHY2U3Ai0cE0vTk40W7NuD9MDtAzxk7TrkkGyH 3IqTo800gmxNpbXAxBykY6o= X-Google-Smtp-Source: AGHT+IFB5Nmp/077FgnvrkfOhjZv6DJxn95d2yF1QE223KQPG0V6QgNWbSTI7lG4sWDoBa8OUEBeIQ== X-Received: by 2002:a05:6e02:214e:b0:357:5e40:6bb5 with SMTP id d14-20020a056e02214e00b003575e406bb5mr3565755ilv.30.1697839244039; Fri, 20 Oct 2023 15:00:44 -0700 (PDT) Received: from moubin (71-36-110-102.ptld.qwest.net. [71.36.110.102]) by smtp.gmail.com with ESMTPSA id j11-20020a63cf0b000000b005afdd58bab2sm1944804pgg.30.2023.10.20.15.00.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 20 Oct 2023 15:00:43 -0700 (PDT) Date: Fri, 20 Oct 2023 15:00:40 -0700 From: Mark Wong To: Thomas Munro Cc: Ronan Dunklau , Devrim =?iso-8859-1?B?R/xuZPx6?= , PostgreSQL Hackers , Fabien COELHO , Andres Freund , Dmitry Dolgov <9erthalion6@gmail.com> Subject: Re: LLVM 16 (opaque pointers) Message-ID: References: <5716086.DvuYhMxLoT@aivenlaptop> <2700884.mvXUDI8C0e@aivenlaptop> 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 Sat, Oct 21, 2023 at 10:48:47AM +1300, Thomas Munro wrote: > On Thu, Oct 19, 2023 at 6:20 AM Thomas Munro wrote: > > Interestingly, a new problem just showed up on the the RHEL9 s390x > > machine "lora", where a previously reported problem [1] apparently > > re-appeared. It complains about incompatible layout, previously > > blamed on mismatch between clang and LLVM versions. I can see that > > its clang is v15 from clues in the conflig log, but I don't know which > > version of LLVM is being used. However, I see now that --with-llvm > > was literally just turned on, so there is no reason to think that this > > would have worked before or this work is relevant. Strange though -- > > we must be able to JIT further than that on s390x because we have > > crash reports in other threads (ie we made it past this and into other > > more advanced brokenness). > > I see that Mark has also just enabled --with-llvm on some POWER Linux > animals, and they have failed in various ways. The failures are > strangely lacking in detail. It seems we didn't have coverage before, > and I recall that there were definitely versions of LLVM that *didn't* > work for our usage in the past, which I'll need to dredge out of the > archives. I will try to get onto a cfarm POWER machine and see if I > can reproduce that, before and after these commits, and whose bug is > it etc. Yeah, I'm slowing enabling --with-llvm on POWER, s390x, and aarch64 (but none here yet as I write this)... > I doubt I can get anywhere near an s390x though, and we definitely had > pre-existing problems on that arch. If you want to send me your ssh key, I have access to these systems through OSUOSL and LinuxFoundation programs. Regards, Mark -- Mark Wong EDB https://enterprisedb.com