Re: C11 / VS 2019
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: David Rowley <dgrowleyml@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-08-26T15:52:36Z
Lists: pgsql-hackers
On 30.07.25 00:11, David Rowley wrote: > On Wed, 30 Jul 2025 at 00:57, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> >> David Rowley <dgrowleyml@gmail.com> writes: >>> On Fri, 18 Jul 2025 at 23:12, Peter Eisentraut <peter@eisentraut.org> wrote: >>>> Note that gcc and clang switched to C11 by default a long time ago >>>> (gcc-5 and clang-3.6), so for most users all these tests won't need to >>>> do anything. If you want to test it, you could simulate an older >>>> default like >>>> ./configure CC='gcc -std=c99' >> >>> On Linux, doing a bit more testing using meson and clang, I tried with >>> CC=clang CFLAGS=-std=c99 . I get: >> >> Note that that's not what Peter suggested. That leads to > > OK, thanks. There are no issues when I use CC="clang -std=c99" meson setup ... This has been committed. C11 is the default mode now. David: You could rebase your other patch (about emulating __builtin_constant_p) now. Tom: You ought to update the configuration on the buildfarm members longfin and sifaka from 'CC' => 'ccache clang -std=gnu99', to 'CC' => 'ccache clang -std=gnu11', for the master branch.
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