On Wed, 2 Nov 2022 16:45:35 GMT, Julian Waters <jwat...@openjdk.org> wrote:
>> [JDK-8241499](https://bugs.openjdk.org/browse/JDK-8241499) proposes to set >> the -permissive- flag for the Microsoft Visual C++ compiler, to enforce >> strict standards conformance during compilation, making native code behave >> more strictly. While adding it to default builds is likely not practical >> given how much testing is required, as an option it can prove helpful in >> finding areas of native code that are not conformant to the standard. >> Instead of applying this to just one compiler, we can also include this for >> every compiler that has support for such a strict mode, which this change >> does. > > Julian Waters has updated the pull request with a new target base due to a > merge or a rebase. The incremental webrev excludes the unrelated changes > brought in by the merge/rebase. The pull request contains seven additional > commits since the last revision: > > - Export not required > - Merge remote-tracking branch 'upstream/master' into permissive > - Merge remote-tracking branch 'upstream/master' into permissive > - Merge remote-tracking branch 'upstream/master' into permissive > - Format > - Keep docs up to date > - New --enable-conforming-compilation option FWIW, `-permissive-` is getting less permissive with every compiler iteration; with MSVC2022 (` C Compiler: Version 19.33.31629`) even hotspot doesn't build. ------------- PR: https://git.openjdk.org/jdk/pull/10912
