RFR: 8305955: Remove Visual C++ specific workaround in javac

Jonathan Gibbons jjg at openjdk.org
Mon Jun 5 17:17:08 UTC 2023


On Thu, 13 Apr 2023 11:36:15 GMT, Julian Waters <jwaters at openjdk.org> wrote:

> Visual C++ no longer requires the use of the i64 literal syntax and instead recommends the use of LL instead, so we should remove this workaround in the JNIWriter (this also helps when users write Windows JNI code meant to be compiled with alternate compilers other than Visual C++)

A conservative solution would be to change the default but provide a mechanism like a hidden option to restore the old behavior in case anyone needs it.

The current behavior is not specified (but that's a different bug!) so a CSR should not be necessary, but in that case, I would advise a [Release Note](https://openjdk.org/guide/#release-notes).

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

PR Comment: https://git.openjdk.org/jdk/pull/13457#issuecomment-1577176688


More information about the compiler-dev mailing list