-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 545605 - Adjust ecj to change in JVMS 4.7.18./19. #2625
Comments
Quite a coincidence that genie reminded me of this bug right after https://mail.openjdk.org/pipermail/compiler-dev/2024-June/026996.html ff 🪄 😄 |
What genie are you are referring to ?? |
The "author" of https://bugs.eclipse.org/bugs/show_bug.cgi?id=545605#c22, which caused an email notification two days ago. |
The exception observed in the original bug reported was the improved diagnostic from https://bugs.eclipse.org/474081 - at which time this structure was illegal indeed. |
Raising visibility of another link hidden in bugzilla: https://bugs.openjdk.org/browse/JDK-8067975 |
Should anybody suspect that the correlation between parameters and their annotations goes astray define a system property
|
Accept class files with mismatching parameter count vis-a-vis parameter annotations (which is legal since Java 9). Also introduces system property jdt.reject.parameterAnnotations.countMismatch to get back the previous error reporting. fixes eclipse-jdt#2625
Accept class files with mismatching parameter count vis-a-vis parameter annotations (which is legal since Java 9). Also introduces system property jdt.reject.parameterAnnotations.countMismatch to get back the previous error reporting. fixes eclipse-jdt#2625
To be continued via #2938 |
from https://bugs.eclipse.org/545605
The essence: ecj may throw in
this happens when reading a class file with a method of this shape:
annotatable parameter count 2 looks "wrong", but according to the same spec sentence we are insisting on in #205, ecj should accept that classfile, whether or not we can make sense of that annotation.
The text was updated successfully, but these errors were encountered: