Re: C11 / VS 2019
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Yura Sokolov <y.sokolov@postgrespro.ru>,
Michael Paquier <michael@paquier.xyz>,
Nathan Bossart <nathandbossart@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-06-04T06:22:14Z
Lists: pgsql-hackers
On 03.06.25 10:01, Yura Sokolov wrote: > Will it mean we can implement atomics in term of C11 atomics? > Aside for VS 2019, which has no support for. (But VS 2022 already has.) > So instead of numerous variants we could just differ VS2019 vs plain C11. I wrote: """ GCC details: The oldest gcc version that we currently need to support is gcc 4.8, which comes with RHEL 7. As alluded to above, some C11 features came later with gcc 4.9, specifically generic, threads, and atomics. I think it would still be useful to move forward without those features. """ So there is additional homework to do there.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Raise C requirement to C11
- f5e0186f865c 19 (unreleased) landed
-
meson: Move C99 test earlier
- 4a4038068bb2 19 (unreleased) landed
-
Enable MSVC conforming preprocessor
- 8fd9bb1d9654 19 (unreleased) landed
-
Make parseNodeString() C idiom compatible with Visual Studio 2015.
- f9f31aa91f82 16.0 cited