Skip to content
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

8283323: libharfbuzz optimization level results in extreme build times #1077

Closed
wants to merge 2 commits into from

Conversation

backwaterred
Copy link
Contributor

@backwaterred backwaterred commented May 9, 2022

This PR backports changes to improve build performance with xlc.

It appears that the file was at make/modules/java.desktop/lib/Awt2dLibraries.gmk when this commit was made, but that file has since been moved to make/lib/Awt2dLibraries.gmk. This made the change show up as a conflict when I applied this backport using the Skara tools. I resolved the 'conflict' by copying the changes to the new path and marking the previous path as removed.


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed (1 review required, with at least 1 reviewer)

Issue

  • JDK-8283323: libharfbuzz optimization level results in extreme build times

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/1077/head:pull/1077
$ git checkout pull/1077

Update a local copy of the PR:
$ git checkout pull/1077
$ git pull https://git.openjdk.java.net/jdk11u-dev pull/1077/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1077

View PR using the GUI difftool:
$ git pr show -t 1077

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/1077.diff

@backwaterred backwaterred marked this pull request as draft May 9, 2022 21:43
@bridgekeeper
Copy link

bridgekeeper bot commented May 9, 2022

👋 Welcome back tsteele! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@backwaterred backwaterred changed the title Backport: 2c43ecb43fa3c94b69478039f1cd70ed4a577768 Backport 2c43ecb43fa3c94b69478039f1cd70ed4a577768 May 9, 2022
@openjdk openjdk bot changed the title Backport 2c43ecb43fa3c94b69478039f1cd70ed4a577768 8283323: libharfbuzz optimization level results in extreme build times May 9, 2022
@openjdk
Copy link

openjdk bot commented May 9, 2022

This backport pull request has now been updated with issue from the original commit.

@openjdk openjdk bot added the backport label May 9, 2022
@backwaterred backwaterred marked this pull request as ready for review May 10, 2022 20:42
@openjdk openjdk bot added the rfr Pull request is ready for review label May 10, 2022
@mlbridge
Copy link

mlbridge bot commented May 10, 2022

Webrevs

Copy link
Contributor

@TheRealMDoerr TheRealMDoerr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You have missed the empty line deletion from the original change. Backports should be as clean and complete as possible. Besides that, LGTM. Note that I have created a clean backport PR for 17u-dev which should be done first: openjdk/jdk17u-dev#392

@backwaterred
Copy link
Contributor Author

You have missed the empty line deletion from the original change. Backports should be as clean and complete as possible.

I appreciate the attention to detail, and have made this change.

Besides that, LGTM. Note that I have created a clean backport PR for 17u-dev which should be done first: openjdk/jdk17u-dev#392

Thanks for opening the change for jdk17, does jdk18 require a backport as well?

Copy link
Contributor

@TheRealMDoerr TheRealMDoerr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks! Would be nice to have in 18u, too, yes. But we don't require it in non-LTS releases.

@openjdk
Copy link

openjdk bot commented May 11, 2022

@backwaterred This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8283323: libharfbuzz optimization level results in extreme build times

Reviewed-by: mdoerr

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 5 new commits pushed to the master branch:

  • 844f03b: 8286630: [11] avoid -std=c++11 CXX harfbuzz buildflag on Windows
  • 7921cc1: 8286198: [linux] Fix process-memory information
  • fa37935: 8285828: runtime/execstack/TestCheckJDK.java fails with zipped debug symbols
  • e793096: 8282293: Domain value for system property jdk.https.negotiate.cbt should be case-insensitive
  • c95c796: 8255787: Tag container tests that use cGroups with cgroups keyword

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@TheRealMDoerr) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 11, 2022
@backwaterred
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label May 13, 2022
@openjdk
Copy link

openjdk bot commented May 13, 2022

@backwaterred
Your change (at version dd7aa20) is now ready to be sponsored by a Committer.

@TheRealMDoerr
Copy link
Contributor

/sponsor

@openjdk
Copy link

openjdk bot commented May 13, 2022

Going to push as commit 9cb3797.
Since your change was applied there have been 5 commits pushed to the master branch:

  • 844f03b: 8286630: [11] avoid -std=c++11 CXX harfbuzz buildflag on Windows
  • 7921cc1: 8286198: [linux] Fix process-memory information
  • fa37935: 8285828: runtime/execstack/TestCheckJDK.java fails with zipped debug symbols
  • e793096: 8282293: Domain value for system property jdk.https.negotiate.cbt should be case-insensitive
  • c95c796: 8255787: Tag container tests that use cGroups with cgroups keyword

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label May 13, 2022
@openjdk openjdk bot closed this May 13, 2022
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels May 13, 2022
@openjdk
Copy link

openjdk bot commented May 13, 2022

@TheRealMDoerr @backwaterred Pushed as commit 9cb3797.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

2 participants