Re: Don't use __builtin_setjmp on aarch64 MinGW/Windows

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Greg Burd <greg(at)burd(dot)me>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Dave Cramer <davecramer(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, John Naylor <johncnaylorls(at)gmail(dot)com>
Subject: Re: Don't use __builtin_setjmp on aarch64 MinGW/Windows
Date: 2026-07-28 15:35:48
Message-ID: amjMVEpTddzOvui5@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 28, 2026 at 09:10:54AM -0400, Greg Burd wrote:
> * clang for aarch64-w64-windows-gnu does not implement
> __builtin_setjmp at all; and

Does clang for x86-64 implement it?

> So on this toolchain the plain setjmp()/longjmp() fallback is not merely
> a compile fix -- it is runtime-correct. The original MinGW-64
> setjmp/longjmp defect that 146cb3889c3 works around appears to be
> specific to the x86_64 GCC MinGW toolchain and not present in
> clang-aarch64-mingw, which has its own setjmp lowering. I have not
> tested a GCC-based aarch64 MinGW toolchain.

Testing on aarch64/gcc/mingw seems like an important step.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-07-28 15:39:19 Re: add list of major features to the v19 release notes
Previous Message Tomas Vondra 2026-07-28 15:29:02 Re: hashjoins vs. Bloom filters (yet again)