| From: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Trying out <stdatomic.h> |
| Date: | 2025-11-19 14:03:03 |
| Message-ID: | CAJ7c6TPz51ZGasiotDp8ftuPB-VLd-2dcsRCooXTCeYAKpDk2Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Thomas,
> It passes with VS 2022 on CI. I had to skip some assertions about
> macros promising lock-free implementation, that it doesn't define in C
> mode yet. They are definitely lock-free though[1], and the macros are
> defined for C++, and the same under the covers... Perhaps
> feature/conformance macros won't be defined until a few remaining
> pieces (things we don't care about) are accessible from C? (I see
> that Visual Studio 2026 has also just shipped a couple of days ago,
> not investigated.)
Thanks for working on this. I checked v2 on Linux x64 with and without
Valgrind and it passed all the tests. I haven't looked at the code
closely yet.
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2025-11-19 14:08:14 | Re: ON CONFLICT DO SELECT (take 3) |
| Previous Message | Peter Eisentraut | 2025-11-19 13:56:59 | Re: [PATCH] Add hints for invalid binary encoding names in encode/decode functions |