RFR: 8292008: Transition the JDK to the common standard of C11

Andrey Turbanov aturbanov at openjdk.org
Tue Aug 30 12:03:07 UTC 2022


On Tue, 30 Aug 2022 09:57:09 GMT, Magnus Ihse Bursie <ihse at openjdk.org> wrote:

> This patch will set C11 as the "language level" for C code in the JDK code base, similar to how we set C++14 for the C++ code.
> 
> At this point, (almost) all our compilers support C11. The "almost" here is the one exception, Visual Studio 2017. I've chosen to keep VS2017 as an accepted compiler, and if that is used, we will still build without C11 as a language level. This is a suboptimal solution however, and I think we should start thinking about removing VS2017 as a supported compiler really soon.
> 
> For further background on the switch to C11, see [JDK-8292008](https://bugs.openjdk.org/browse/JDK-8292008) and [this mail](https://mail.openjdk.org/pipermail/jdk-dev/2022-August/006826.html).
> 
> I have tested this patch with Tier 1-3 in Oracle's internal CI system.

make/autoconf/flags-cflags.m4 line 549:

> 547:     else
> 548:       # Visual Studio 2017 does not support the full C11, nor any other well-defined C standard.
> 549:       # We use the default, which is roughly C89 + certain chosen extensions. CS2017 will need to

>`CS2017`

did you mean VS 2017 ?

-------------

PR: https://git.openjdk.org/jdk/pull/10077



More information about the build-dev mailing list