-
Notifications
You must be signed in to change notification settings - Fork 729
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
Add methods to check if array class can be trusted as fixed class #20853
base: master
Are you sure you want to change the base?
Add methods to check if array class can be trusted as fixed class #20853
Conversation
The upstream APIs are created in eclipse-omr/omr#7579. @hzongaro May I ask you to review this change? Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the changes look correct. Just one suggestion.
5964e8c
to
da631ba
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May I ask you to provide a bit more information in the commit comment about the circumstances in which these changes apply? Perhaps you can copy some of the comments you currently have in the upstream OMR commit. Also, the first line of the commit comment is 73 characters long. Per the commit guidelines, it should be less than 70 columns.
If null-restricted array is enabled and the class is an array class, the null-restricted array class and the nullable array class share the same signature. The null-restricted array can be viewed as a sub-type of the nullable array. Therefore, the constraint cannot be fixed class. Related: eclipse-openj9#20522 Signed-off-by: Annabelle Huo <[email protected]>
da631ba
to
4b5152e
Compare
@hzongaro All comments are addressed. Ready for another review. Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks! I will wait until the corresponding OMR changes have been promoted before running testing and merging this change.
Jenkins test sanity.functional,sanity.openjdk xlinux,plinux jdk8,jdk17,jdk23 |
Jenkins test sanity.functional xlinuxval jdknext |
Jenkins test sanity.functional xlinuxvalst jdknext |
I'm running internal testing of the x86-64_linux_vt_standard to see whether the failures that were seen are seen without these changes. |
Jenkins test sanity.functional xlinuxvalst jdknext |
There are 3 failed tests in the latest
However, the previous
@hzongaro Thank you for running all the tests! Let's hold off merging this PR for now. I'll take a look at the above crash first. |
@hzongaro I'm able to reproduce the crash in
|
If null-restricted array is enabled and the class is an array class, the null-restricted array class and the nullable array class share the same signature. The null-restricted array can be viewed as a sub-type of the nullable array. Therefore, the constraint cannot be fixed class.
Related: #20522