-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
JDK-8348597 : Update HarfBuzz to 10.4.0 #23910
base: master
Are you sure you want to change the base?
Conversation
👋 Welcome back honkar! A progress list of the required criteria for merging this PR into |
@honkar-jdk This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 78 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
@honkar-jdk The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
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.
Build change looks ok.
The clang users on Linux may want to check if the same new warning triggers there.
/reviewers 2
@@ -129,6 +131,7 @@ | |||
#pragma GCC diagnostic ignored "-Wclass-memaccess" | |||
#pragma GCC diagnostic ignored "-Wcast-function-type-strict" // https://github.com/harfbuzz/harfbuzz/pull/3859#issuecomment-1295409126 | |||
#pragma GCC diagnostic ignored "-Wdangling-reference" // https://github.com/harfbuzz/harfbuzz/issues/4043 | |||
#pragma GCC diagnostic ignored "-Wdangling-pointer" // Trigerred by hb_decycler_node_t(). |
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.
@prrace With the latest harfbuzz (v10.4.0), dangling-pointer warning is ignored. With this addition, I assumed that we no longer need to add it to harfbuzz warning section explicitly.
But without adding dangling-pointer to HARFBUZZ_DISABLED_WARNINGS_gcc
build fails on linux so probably JDK build requires warnings to be explicitly added to ClientLibraries.gmk ?
decycler.hh:110:25: error: storing the address of local variable ‘decycler_node'
in '((hb_decycler_t*)((char*)scratch + 8))[1].hb_decycler_t::tortoise' [-Werror=dangling-pointer=]
110 | decycler.tortoise = decycler.hare = this;
| ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
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.
Interesting. I also would have expected this to over-ride the JDK default.
But if that's what you see ...
A bit of googling suggests that sometimes these pragmas are read too late.
@@ -53,9 +53,9 @@ STEP 2: BUILD CHANGES INCREMENTALLY | |||
|
|||
STEP 3: COMPILER WARNINGS AND SETTING FLAGS | |||
------------------------------------------- | |||
- Update make parameters in Awt2DLibraries.gmk | |||
- Update make parameters in make/modules/java.desktop/lib/ClientLibraries.gmk |
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.
good catch
@@ -129,6 +131,7 @@ | |||
#pragma GCC diagnostic ignored "-Wclass-memaccess" | |||
#pragma GCC diagnostic ignored "-Wcast-function-type-strict" // https://github.com/harfbuzz/harfbuzz/pull/3859#issuecomment-1295409126 | |||
#pragma GCC diagnostic ignored "-Wdangling-reference" // https://github.com/harfbuzz/harfbuzz/issues/4043 | |||
#pragma GCC diagnostic ignored "-Wdangling-pointer" // Trigerred by hb_decycler_node_t(). |
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.
Interesting. I also would have expected this to over-ride the JDK default.
But if that's what you see ...
A bit of googling suggests that sometimes these pragmas are read too late.
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 had to use webrev to review. github was too painfully slow.
Harfbuzz upgraded to v10.4.0
File changes -
Newly added files
Deleted
Modified: 182 existing files modified
To prevent build failures due to dangling pointer (on linux) it has been added to HARFBUZZ_DISABLED_WARNINGS_gcc in ClientLibraries.gmk
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23910/head:pull/23910
$ git checkout pull/23910
Update a local copy of the PR:
$ git checkout pull/23910
$ git pull https://git.openjdk.org/jdk.git pull/23910/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23910
View PR using the GUI difftool:
$ git pr show -t 23910
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23910.diff
Using Webrev
Link to Webrev Comment