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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Greg Burd <greg(at)burd(dot)me>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
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 21:10:57
Message-ID: 446e5d78-2e97-4c73-a78c-50c6a093b56f@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2026-07-28 Tu 1:46 PM, Greg Burd wrote:
>
>> Testing on aarch64/gcc/mingw seems like an important step.
> Agreed, and I want to be upfront that I have not been able to test that
> combination yet -- I don't currently have an aarch64 GCC MinGW toolchain
> (the llvm-mingw / MSYS2 clangarm64 toolchain I build with is clang-based,
> which is where the aarch64 buildfarm work has been happening). So the
> runtime evidence I offered ("25/25 elog(ERROR)->siglongjmp cycles, nested
> PL/pgSQL exceptions, no crash") is specifically for clang-aarch64-mingw,
> whose setjmp lowering is its own thing. I should not have implied
> anything broader.

My understanding is that there is no such animal on the horizon, that
all the MSYS team's aarch64 efforts are concentrated on clang, which is
why there is no native Strawberry perl for aarch64 (They are too deeply
invested in gcc). What fun, eh?

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Burd 2026-07-28 21:27:32 Re: Don't use __builtin_setjmp on aarch64 MinGW/Windows
Previous Message Jeff Davis 2026-07-28 21:09:31 Re: [Bug] pg_upgrade could fail for non-superuser subscriptions using foreign servers