-
Notifications
You must be signed in to change notification settings - Fork 722
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
jdknext build problems String.getBytes() #11312
Comments
@JasonFengJ9 @tajila @babsingh fyi I'll disable the jdknext acceptance until resolved. |
@hangshao0 Can you take a look at this. It looks like the signature for |
New
|
New
|
There are some other changes to Lookup regarding hidden classes, I've opened an issue to track it, #11321. |
New
|
This PR can track the string changes |
The above three suggested changes should allow us to re-enable jdknext builds: |
@babsingh Can you open a PR for the String changes |
I will open a PR for all three changes since all are standalone changes, and they will need to be in one PR to test successful JDK16 compilation. |
Related: eclipse-openj9#11312 Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
The new Lookup.ORIGINAL field (= 0x40) conflicts with Lookup.INTERNAL_PRIVILEGED. Since INTERNAL_PRIVILEGED is J9 specific, it is given a different value (= 0x80). In JDK16, defineHiddenClassWithClassData has changed to a public method; and the initOption is supplied by the caller instead of it always being true. Related: eclipse-openj9#11312 eclipse-openj9#11321 Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
https://ci.eclipse.org/openj9/job/Pipeline-OpenJDK-Acceptance/390/
The text was updated successfully, but these errors were encountered: