-
Notifications
You must be signed in to change notification settings - Fork 114
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
[Backport] 18309: fix of jdk-8180450 #892
[Backport] 18309: fix of jdk-8180450 #892
Conversation
6cc9014
to
c33ba5c
Compare
0a7c8d6
to
71bac6a
Compare
Summary:Backport the fix of issue JDK-8180450 to dragonwell 11 Testing: JTreg Reviewers: Kuaiwei, wenjie Issue: https://github.com/dragonwell-project/dragonwell11/issues/893a
71bac6a
to
89628ae
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.
LGTM
There are also several JDK bugs related to JDK-8180450. |
Summary: Port Optimize Klass layout after JDK-8180450 to dragonwell 11 Testing: jtreg Issue: https://bugs.openjdk.org/browse/JDK-8334220
Backported: Won't backport others for RISC-V, PPC64 and the improving patch for C1 and interpreter. |
Summary: 8332498: [aarch64, x86] improving OpToAssembly output for partialSubtypeCheckConstSuper Instruct Testing: jtreg Issue: https://bugs.openjdk.org/browse/JDK-8332498
7438ec9
to
77bdab9
Compare
I saw the same build error message for win-x64 platform: It seems related to this commit. |
Summary: 8295414: [Aarch64] C2: assert(false) failed: bad AD file Issue: https://bugs.openjdk.org/browse/JDK-8295414
Should backport this fix https://bugs.openjdk.org/browse/JDK-8295414, too |
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.
It looks good to me.
It would be better to do full jtreg test on all our available platforms.
The type pollution issue of JDK causes significant performance slowing down when type is checked concurrently.
The upstream has fixed this issue for JDK 24 and 22. This PR backports the fix to JDK11.