Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade

On Thu, Jun 5, 2025 at 8:48 PM Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
> > Hmm, for the purposes of [0], I think it might be better to keep the
> > image at VS 2019 for now.  Unless there are specific reasons why VS 2022
> > would be of use now?
>
> Thomas was thinking of trying some new APIs which are available in the
> VS 2022, he may answer this better.

My goal in asking about that was to have the infrastructure to advance
the Windows-on-aarch64 project (as a non-Windows developer trying to
advance things based on standards instead of hand-rolling), since
that's apparently where their <stdatomic.h> support was added, and I
speculate that that is the best way forward for porting our atomics to
new platforms:


https://www.postgresql.org/message-id/flat/CADK3HHL9hJnCxttPnhPvdNdXC_7ger%3DiarMMy0KOrOOweaMAxw%40mail.gmail.com#75363fb1078b930736ad7fc7b9f95910

I think on your C11 thread I might have been confused about that,
since there was an implication that 2019 might support <stdatomic.h>,
but it looks like 2019 added language stuff while 2022 added the
library stuff.  But yeah, given your proposal that MSVC 2019 should be
our new minimum target on that platform, I wonder if we should have
both available in CI somehow...

(Trying to constrain the window of MSVC support to just "the two
latest major releases" in future is also an attractive idea, as seen
in some other big open source C/C++ projects, given our lack of
Windows-native developers and reliance on CI, but let's call that a
separate debate.)