Re: Trying out <stdatomic.h>

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.