-
Notifications
You must be signed in to change notification settings - Fork 171
8315020: The macro definition for LoongArch64 zero build is not accurate. #489
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
Conversation
|
👋 Welcome back lzhai! A progress list of the required criteria for merging this PR into |
|
❗ This change is not yet ready to be integrated. |
Webrevs
|
|
Could you review and sponsor the patch please? Thanks, |
|
/approval request allow Zero build on LoongArch |
|
@xiangzhai |
common/autoconf/platform.m4
Outdated
| # ZERO_ARCHDEF is used to enable architecture-specific code | ||
| case "${OPENJDK_TARGET_CPU}" in | ||
| loongarch64) ZERO_ARCHDEF=LOONGARCH64 ;; |
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.
This is not necessary, line 390 already does that.
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.
But the line 390 is for x86, isn't it? Please point out my fault!
Thanks,
Leslie Zhai
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.
The other 390 ;-) 391 after the patch.
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.
The *) case.
| #elif (defined AARCH64) | ||
| static Elf32_Half running_arch_code=EM_AARCH64; | ||
| #elif (defined LOONGARCH) | ||
| #elif (defined LOONGARCH64) |
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.
+1, this fixes the compile issue I reported.
|
Mailing list message from Thorsten Glaser on jdk8u-dev: On Sun, 28 Apr 2024, Leslie Zhai wrote: There?s an unnecessary line in there, I noted that on the web thingy. The failing s390x build is because this is still using Do an s!http://(httpredir|deb).debian.org!http://archive.debian.org!g bye, |
|
@xiangzhai This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
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.
The PR title should be "Backport 725ec0ce1b463b21cd4c5287cf4ccbee53ec7349" so this is correctly recognised as a backport.
I agree with @mirabilos that the platform.m4 change is unneeded. That block is only needed where ZERO_ARCHDEF and OPENJDK_TARGET_CPU_LEGACY_LIB differ e.g. ppc vs. ppc32 or x86_64 vs. amd64. The ppc64 one is also unnecessary but I wouldn't change this at this juncture.
I'm also leaning towards thinking we should file this against https://github.com/openjdk/jdk8u to get it in as a fix for July rather than waiting for October. The risk to other architectures should be zero, while this makes the new platform build. Sorry for not getting to this earlier so it would go in before rampdown. Thoughts?
Did the original version build on some LoongArch64 platforms? I'm wondering how this got through the original testing.
|
This backport pull request has now been updated with issue from the original commit. |
|
Hi @gnu-andrew Could you review my patch again please? Thanks, |
Updated patch looks fine, but can we please open this as a PR against https://github.com/openjdk/jdk8u ? We can then get this fixed in the July release, but we only have next week to do this. Thanks. |
Could you review the patch please? openjdk/jdk8u#56 Thanks, |
|
This one needs to close if it gets integrated with openjdk/jdk8u#56 |
Hi,
I'd like to backport this patch to jdk8u.
common/autoconf/platform.m4andhotspot/src/os/linux/vm/os_linux.cppdo not apply cleanly due to context difference, but it is easy to resolve them manually.A native build on LoongArch hardware is tested.
Debian: https://mail.openjdk.org/pipermail/jdk8u-dev/2024-April/018378.html
Loongnix Desktop:
The risk of the downport is low.
Thanks,
Leslie Zhai
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev.git pull/489/head:pull/489$ git checkout pull/489Update a local copy of the PR:
$ git checkout pull/489$ git pull https://git.openjdk.org/jdk8u-dev.git pull/489/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 489View PR using the GUI difftool:
$ git pr show -t 489Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/489.diff
Webrev
Link to Webrev Comment