-
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
8300169: Build failure with clang-15 #12005
Conversation
👋 Welcome back jiefu! A progress list of the required criteria for merging this PR into |
@DamonFool 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. |
@@ -188,7 +188,7 @@ template <> struct hb_int_max<signed long long> : hb_integral_constant<s | |||
template <> struct hb_int_max<unsigned long long> : hb_integral_constant<unsigned long long, ULLONG_MAX> {}; | |||
#define hb_int_max(T) hb_int_max<T>::value | |||
|
|||
#if defined(__GNUC__) && __GNUC__ < 5 | |||
#if defined(__GNUC__) && __GNUC__ < 5 && !defined(__clang__) |
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.
Normally, such changes in third-party libraries need to be done upstream, and not locally. @prrace can confirm.
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.
Normally, such changes in third-party libraries need to be done upstream, and not locally. @prrace can confirm.
Thanks @kevinrushforth for your review.
Yes, it had been fixed in the upstream and I just follow it.
Please see https://github.com/harfbuzz/harfbuzz/blob/main/src/hb-meta.hh#L202 .
Or did you mean we had to sync the whole harfbuzz with the upstream?
If so, I would suggest doing it in a separate PR.
What do you think?
Thanks.
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.
No, I didn't mean to update all of harfbuzz. What you've done seems fine to me, but let's see what @prrace says.
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.
If the exact same change has been committed upstream then we are OK to take this because then when we upgrade harfbuzz (under a separate bug) whoever doing the upgrade can be blissfully ignorant of this. In fact it is because there is no easy way to be track changes on the JDK side and reapply them that we have this rule.
Is there a list of the issues building libjli? I don't see the in the PR or the JBS issue. For the libzip issues, are these in the native methods or when compiling the zlib code, just wondering if there are bug reports for upstream there too. |
Thanks @AlanBateman for the review. Here is the bug report while building libjli (target support_native_java.base_libjli_zadler32.o).
|
Mainly caused by files under |
Maybe this one: |
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.
Hotspot changes are good.
Thanks.
@DamonFool 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 39 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 |
Thanks @dholmes-ora . |
Hi @kevinrushforth and @AlanBateman , are you fine with this change? |
Yes, but I would wait for @prrace to review the Harfbuzz change. |
No objection from me but I agree with Kevin to wait to see what Phil says about Harfbuzz. |
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.
client changes are OK by me.
Mailing list message from Patrick Chen on build-dev: no you have to revert the commit Le mar. 17 janv. 2023 ? 17:55, Alan Bateman <alanb at openjdk.org> a ?crit : -------------- next part -------------- |
Why?
|
Thanks @prrace . |
/integrate |
Going to push as commit 15a9186.
Your commit was automatically rebased without conflicts. |
@DamonFool Pushed as commit 15a9186. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi all,
Please review the fix for the build failure with clang-15.
Ref: https://github.com/harfbuzz/harfbuzz/blob/main/src/hb-meta.hh#L202
Thanks.
Best regards,
Jie
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/12005/head:pull/12005
$ git checkout pull/12005
Update a local copy of the PR:
$ git checkout pull/12005
$ git pull https://git.openjdk.org/jdk pull/12005/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 12005
View PR using the GUI difftool:
$ git pr show -t 12005
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12005.diff