> 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
On Tue, 30 Aug 2022 14:31:48 GMT, Magnus Ihse Bursie 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 exceptio
On Tue, 30 Aug 2022 11:59:43 GMT, Andrey Turbanov wrote:
>> Magnus Ihse Bursie has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fix typo
>
> make/autoconf/flags-cflags.m4 line 549:
>
>> 547: else
>> 548: # Visual Studio 2017 do
> 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
On Tue, 30 Aug 2022 09:57:09 GMT, Magnus Ihse Bursie 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, Vi
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, a
