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.96) (envelope-from ) id 1wrcP4-0000ZY-1B for pgsql-bugs@arkaria.postgresql.org; Wed, 05 Aug 2026 14:15:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wrcP3-0008a0-2z for pgsql-bugs@arkaria.postgresql.org; Wed, 05 Aug 2026 14:15:29 +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.96) (envelope-from ) id 1wrcP3-0008Zs-2E for pgsql-bugs@lists.postgresql.org; Wed, 05 Aug 2026 14:15:29 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wrcP0-00000000OfD-01Mx for pgsql-bugs@lists.postgresql.org; Wed, 05 Aug 2026 14:15:28 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 675EFHmn1328666; Wed, 5 Aug 2026 10:15:17 -0400 From: Tom Lane To: =?UTF-8?B?0JDRgNGC0ZHQvCDQl9Cw0YDRg9Cx0LjQvQ==?= cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #19609: Server crashes when executing a JIT-compiled SQL function on s390x In-reply-to: References: <19609-e5278efcee2b4419@postgresql.org> Comments: In-reply-to =?UTF-8?B?0JDRgNGC0ZHQvCDQl9Cw0YDRg9Cx0LjQvQ==?= message dated "Wed, 05 Aug 2026 18:20:49 +0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1328664.1785939317.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 05 Aug 2026 10:15:17 -0400 Message-ID: <1328665.1785939317@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =3D?UTF-8?B?0JDRgNGC0ZHQvCDQl9Cw0YDRg9Cx0LjQvQ=3D=3D?=3D writes: > I am attaching the TAP test mentioned in the bug report. If the same test doesn't fail on other arches (x86, arm, etc) then this is almost certainly an LLVM bug, and you should be reporting it to them. regards, tom lane