-
-
Notifications
You must be signed in to change notification settings - Fork 255
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
jdk11u-linux-aarch64-dragonwell : /usr/bin/bash: line 1: 41820 Illegal instruction #2454
jdk11u-linux-aarch64-dragonwell : /usr/bin/bash: line 1: 41820 Illegal instruction #2454
Comments
@joeyleeeeeee97 FYI |
FWIW I can build dragonwell JDK11 on my CentOS7/aarch64 machine build-packet-centos74-armv8-1 without issues - build log attached. Here is the version output:
|
Could we restrict this on Alibaba's recently donated machines and see how it goes? Thanks |
Hmmm it does seem to work on the alibaba machine based on https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-aarch64-dragonwell/16/ which initially makes me wonder if there's any hardware specific assembler in there. Running |
I now believe this to be happening due to the |
@joeyleeeeeee97 Is this locking to certain types of aarch64 hardware intentional? |
Reopening until we know what we want to target |
@sxa Yes.. Refer to We will alter this to-march=armv8.1 later |
Would you expect Also is there a timeline for switching? |
@sxa After an internal discussion, we decided to keep that |
That limit has already been done in https://github.com/AdoptOpenJDK/ci-jenkins-pipelines/pull/61/files - I was expecting that to be temporary but sounds like it'll need to stay there. We will need to carefully consider at adopt what we call this version since it's not a straight aarch64 port and we don't want to give false hope to people which might result in extra bug reports (bearing in mind it doesn't work on the four other |
Closing since the immediate problem has been solved but I'll raise another one to discuss naming of any builds that target the updated version of the architecture |
https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-aarch64-dragonwell/2/console
The text was updated successfully, but these errors were encountered: