Cannot compile with openjdk17 and gcc[89] with Intel opencl. #145
Assignees
Labels
Projects
Comments
|
Hi @yazun . OpenJDK 17 is not supported yet. Quite likely, the error you are getting is because the Graal version shipped in OpenJDK 17 has minor changes that we need to address and support. Currently, we can run OpenJDK 8, 11 and 16 and Graal 21.2.0. These are the backends and the configurations supported: |
|
Hello @jjfumero, |
|
Yes, you are right. It is in our plans to upgrade to JDK17, meanwhile, if possible, you can give it a try with older versions, such as OpenJDK 16, or 11. Hope this helps. |
|
We just finished a greater effort to move to JDK17 so we would be happy to try TornadoVM once the updated to latest JVMCI. |
|
Thank you for your interest. I will leave this thread open. Once we support JDK17 we will post it here. |
|
Thank you, appreciated! |
|
Hi @yazun , https://github.com/beehive-lab/TornadoVM/commits/develop $ tornado -version
WARNING: Using incubator modules: jdk.incubator.foreign, jdk.incubator.vector
openjdk version "17.0.1" 2021-10-19
OpenJDK Runtime Environment (build 17.0.1+12-39)
OpenJDK 64-Bit Server VM (build 17.0.1+12-39, mixed mode)$ tornado --version
version=0.13-dev
branch=develop
commit=d61859bPlease, let us know if this works for you, and feel free to open new issues if you encounter new problems or want to add your feedback. Juan |
|
That's excellent news! |
|
A minor annoyance: Log of the failing compoile without fresh clone, after the The version with mvn -X can be found here: https://pastebin.com/1kyh2jLf |
|
After the successful compilation we get error trying to run examples: |
|
@jjfumero Let me know if you'd prefer a new issue to be created for this one. |
Looks like openjdk added timestamp to the version string without the minor version. |
|
Thanks for the report. I am trying to reproduce the error but it seems you are using an older version. Are you using the latest $ git clone https://github.com/beehive-lab/TornadoVM/
$ cd TornadoVM && git checkout develop
$ export PATH=$PWD/bin/bin:$PATH ## This directory will be automatically generated during Tornado compilation
$ export TORNADO_SDK=$PWD/bin/sdk ## This directory will be automatically generated during Tornado compilation
$ export CMAKE_ROOT=/usr
$ export JAVA_HOME=/home/juan/jvms/graalvm-ce-java17-21.3.0 ## USE YOUR PATH HERE
$ make We changed the default GC to Let me know if this works. Otherwise please, open a new issue with the bug report. |
|
I can confirm that version parsing was the problem - when kludging it with removal of minor version JDK checks at lines 121 and 285: it worked! We have probably the first released JDK17 installed with no minor versions yet. |
|
Great. I will close this issue then. Feel free to open new issues if you encounter new problems. |
|
As a side note the github maven repo you provide still does not have ver 0.13 jars. Can we use 0.12 jars to use with 0.13 distribution? |
|
Yes, that's right. Our maven repos only ship the releases. What you propose will also work because we rarely change the API. We haven't scheduled any changes for the next release regarding the API, so it will keep as it is for now. What we do internally is to use Hope this helps |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Trying to compile on Centos 7 with opencl support on devtoolset-8 and devtoolset-9 :
How To Reproduce
Expected behavior
Successful compilation.
Computing system setup (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: