-
Notifications
You must be signed in to change notification settings - Fork 108
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
8309622: Re-examine the cache mechanism in BaseLocale #1349
base: master
Are you sure you want to change the base?
Conversation
/issue JDK-8309622 |
👋 Welcome back goetz! A progress list of the required criteria for merging this PR into |
❗ This change is not yet ready to be integrated. |
@GoeLin The primary solved issue for a PR is set through the PR title. Since the current title does not contain an issue reference, it will now be updated. |
@GoeLin |
@GoeLin |
@GoeLin The primary solved issue for a PR is set through the PR title. Since the current title does not contain an issue reference, it will now be updated. |
@GoeLin |
This backport pull request has now been updated with issue from the original commit. |
/issue JDK-8331932 |
@GoeLin |
I am thinking about backporting 8309622: Re-examine the cache mechanism in BaseLocale
We see tests
gc/shenandoah/TestAllocIntArrays.java#aggressive and
gc/shenandoah/TestAllocIntArrays.java#iu-aggressive
fail regularly in our CI which is fixed by this change.
Unfortunately 8309622 is not a trivial change. It has one follow-up bug fix and three fixes to startup performance.
So I would have to backport 5 changes.
Luckily, these changes apply clean, except for deleting of src/java.base/share/classes/sun/util/locale/LocaleObjectCache.java because "8316557: Make fields final in 'sun.util' package" is not in 21.
Also, the change is live since 23 including all but one of the follow-ups, so it's pretty well tested.
This PR is only experimental and for discussion. I would backport 8309622 and the bugfix 8328261 in one change, and the three performance fixes as follow-ups.
Alternatively, we could ProblemList the two tests in 21 pointing to 8309622.
For 17, where we see the failure as well, I would prefer the problem listing. This change would not apply well in 17, e.g. it requires JDK-8310913 as prerequisite.
Progress
Warning
8328261: public lookup fails with IllegalAccessException when used while module system is being initialized
Issues
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/1349/head:pull/1349
$ git checkout pull/1349
Update a local copy of the PR:
$ git checkout pull/1349
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/1349/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1349
View PR using the GUI difftool:
$ git pr show -t 1349
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/1349.diff