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 1sJadK-005kfm-O2 for pgsql-bugs@arkaria.postgresql.org; Tue, 18 Jun 2024 15:20:30 +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 1sJadI-00FBAL-52 for pgsql-bugs@arkaria.postgresql.org; Tue, 18 Jun 2024 15:20:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJadH-00FB9M-Nv for pgsql-bugs@lists.postgresql.org; Tue, 18 Jun 2024 15:20:28 +0000 Received: from mail-pf1-x42c.google.com ([2607:f8b0:4864:20::42c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sJadF-001vcA-Rx for pgsql-bugs@postgresql.org; Tue, 18 Jun 2024 15:20:27 +0000 Received: by mail-pf1-x42c.google.com with SMTP id d2e1a72fcca58-70627716174so248016b3a.3 for ; Tue, 18 Jun 2024 08:20:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20230601.gappssmtp.com; s=20230601; t=1718724025; x=1719328825; darn=postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=2kKGXCPWjErpPtVycgS+CxyZGAyIpKwnQs90QzyXfxI=; b=JycBgIjkk75GctfQFHIlSH6zC22CEivVvG2OIU0bOIr9slkJyYoeDfbfhHEmvSiL09 vQm0kUSKHTY5+WJqI31LY6SSafWhW6CoG7aDhD1BI8Dh2bGJR1GZapmSwYGyakyMvII3 WvqnX0ShhhPl/swUWbPwsBhMlQ/L7reOK6iAkHDOHTmGxZCNnvz98HHTiTs/ijya069Y iXtxIaLC3BPvbDRAzDDeuFf7o9FtD8DUUdyelL11GB5I8NnVXI0VSK5LVuSavYveVJnq WF6t4s6ZnBCjd2V154RetA6kFd5P5f/6xSqi+b3frr8w6X7peTEhmUV4gq1YIVK8frnB xdJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718724025; x=1719328825; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=2kKGXCPWjErpPtVycgS+CxyZGAyIpKwnQs90QzyXfxI=; b=gctp0izBzfggVTNXVg8JyVczZWzXEFHbinlcHhHqGE9eWX2JMSSx1i+7QNFUSoE37I JDp7E1e+GII9F9hj7kgoCIXdevgafqi/8Z7OqoEUf344DtSlBwL2XHfiSNX4VunFin24 c+wklcoVaJzGREl4MPYC4EvgrT6WEF9DlmXAX6eWHf90LH5iWLsk6chTAiCM32GnFJpJ 0yLNFr1/LBSIZRTSB7oiJaC/8tdTZJdE/VPOtUYeI8HkfFEz4tjG1rpQvtrPNakjWU0/ IgaGo59PK1X/R506L0iyxkP+lwliy8XMtC2teqxxt0XQnAFsq79RiyrwTKwfZciLx13X Qnog== X-Gm-Message-State: AOJu0Yx1PwahPWsF1OeNo1QcYgGgugN8Bx45OJxCHEhO8fDY2YAVLAdw exbSHMLJ5ZLFKINLc70Yla5G6IJo/NWPX44cLnVXPFZpTmpZNXCbjApPZZ4cu0Mfvxn0sWETWgw = X-Google-Smtp-Source: AGHT+IEcZSWhlrcJdGKlMn041ufb+SbXWPpxzXLQxhG1irjx5x7vO3VfSUKtHthhY5rkO1DJOEcV+A== X-Received: by 2002:a05:6a00:4fc5:b0:705:e621:75af with SMTP id d2e1a72fcca58-705e6218474mr12379503b3a.2.1718724024875; Tue, 18 Jun 2024 08:20:24 -0700 (PDT) Received: from [10.0.67.35] ([50.237.67.30]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-705ccb8f3desm9052346b3a.201.2024.06.18.08.20.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 18 Jun 2024 08:20:24 -0700 (PDT) Message-ID: <12ffcc04d27a6677238a8ab8572a2bffc66c8fdf.camel@j-davis.com> Subject: Re: JIT crash introduced by 6185c9737c with LLVM 14 From: Jeff Davis To: Amit Langote Cc: pgsql-bugs@postgresql.org, Amit Langote Date: Tue, 18 Jun 2024 08:20:22 -0700 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4-0ubuntu2 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2024-06-18 at 15:11 +0900, Amit Langote wrote: > Also, could you please check if the crash still occurs after applying > the attached patch which removes the changes that 6185c9737c made to > files under src/backend/jit? >=20 > (My colleague David Rowley offered to test it on a raspberrypi and on > a x86_64 machine with libLLVM-14.so, but sees no crash using those > steps.) My testcase was wrong because I was installing into the same destination directory each time when bisecting (that shortcut normally works but can cause problems with LLVM changes). When I install into a fresh directory, it works. There may (or may not) have been some bug in my original larger case, but I'll have to re-investigate, and in any case I don't think your commit was a problem. Regards, Jeff Davis