public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Thomas Munro <[email protected]>
To: Heikki Linnakangas <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Trying out <stdatomic.h>
Date: Wed, 19 Nov 2025 12:23:25 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+hUKG+bub1T9TFLUAJHr+Z519VRgJS5tb10xBxEtJZRH8GXiA@mail.gmail.com>
References: <CA+hUKGKFvu3zyvv3aaj5hHs9VtWcjFAmisOwOc7aOZNc5AF3NA@mail.gmail.com>
<[email protected]>
<CA+hUKG+bub1T9TFLUAJHr+Z519VRgJS5tb10xBxEtJZRH8GXiA@mail.gmail.com>
On 13.11.25 12:35, Thomas Munro wrote:
> 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.)
Note also that we still have buildfarm members with gcc <4.9, which is
required for stdatomic.h/_Atomic there.
We could most likely resolve to get rid of them when the time comes, but
let's not forget to plan that.
view thread (19+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Trying out <stdatomic.h>
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox