RFR: 8305955: Remove Visual C++ specific workaround in javac [v2]

Julian Waters jwaters at openjdk.org
Tue Jul 11 06:25:17 UTC 2023


On Fri, 23 Jun 2023 02:45:25 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++)
>
> 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 two additional commits since the last revision:
> 
>  - Merge branch 'openjdk:master' into patch-2
>  - Remove Visual C++ specific workaround in javac

Alright, I've reopened the CSR now. There is already a Release Note:


> Release Note created as https://bugs.openjdk.org/browse/JDK-8309551
> 
> > @TheShermanTanker only [Reviewers](https://openjdk.org/bylaws#reviewer) can determine that a CSR is not needed.
> 
> ...

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

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


More information about the compiler-dev mailing list