-
Bug
-
Resolution: Fixed
-
P3
-
repo-valhalla
The issue happens when javac compiles a Java source file referencing a class provided as a class file (not a source file) and this source file has an invalid access flags combination. In this scenario, javac fails to detect the invalid flags, generates a class file with an incorrect bytecode sequence and considers the compilation to be successful.
Such invalid access flags can easily be detected at compilation time and should trigger an error in the compilation.
Such invalid access flags can easily be detected at compilation time and should trigger an error in the compilation.
- relates to
-
JDK-8297199 [lworld] relocate test folder
- Resolved