> 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.

Magnus Ihse Bursie has updated the pull request with a new target base due to a 
merge or a rebase. The pull request now contains four commits:

 - Remove VS2017 solution
 - Merge branch 'master' into use-c11
 - Fix typo
 - 8292008: Transition the JDK to the common standard of C11

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

Changes: https://git.openjdk.org/jdk/pull/10077/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=10077&range=02
  Stats: 13 lines in 1 file changed: 0 ins; 10 del; 3 mod
  Patch: https://git.openjdk.org/jdk/pull/10077.diff
  Fetch: git fetch https://git.openjdk.org/jdk pull/10077/head:pull/10077

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

Reply via email to