-
Notifications
You must be signed in to change notification settings - Fork 15
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
[24.1] October CPU sync #800
Conversation
…Windows. PullRequest: graal/18413
PullRequest: graal/18779
(cherry picked from commit 3ce4246)
(cherry picked from commit fb9b6c0)
(cherry picked from commit 439d980)
(cherry picked from commit f74bff6)
PullRequest: graal/18806
…sions. PullRequest: graal/18797
…config is specified. PullRequest: graal/18796
…lation logs. PullRequest: graal/18799
…rsing in the agent or configure tool
PullRequest: js/3257
… in VirtualFileSystem. PullRequest: graalpython/3475
PullRequest: graal/18626
…UnimplementedGraalIntrinsics. PullRequest: graal/18563
…mory. (cherry picked from commit 42bb571)
…ion. This allows hoisting bounds checks for memory accesses that are guaranteed to stay within the initial bounds. (cherry picked from commit 7b622f6)
…memory 0. (cherry picked from commit e337757)
…uncher feature on Windows. PullRequest: graal/18683
…field. PullRequest: graal/18798
… and simplify ByteArrayWasmMemory. PullRequest: graal/18855
…chability-metadata.json PullRequest: graal/18819
PullRequest: graal/18854
…es as our Maven plugin. PullRequest: graalpython/3476
PullRequest: graal/18905
PullRequest: graal/18901
PullRequest: graalpython/3474
I'll take a look tomorrow. Thanks! |
Build fails with:
... which should be fixed with this backport graalvm/mandrel-packaging#458 |
@zakkak Is this an actual problem? This PR builds fine for me on
So does this block this PR from getting merged? |
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 seems fine.
I'd suggest trying to merge graalvm/mandrel-packaging#458 and trigger another CI build with this. |
The CI is now fetching When building locally I was getting a JVMCI version mismatch with In any case, there is indeed nothing blocking this PR any more. Once the CI completes I will merge it (probably tomorrow morning) unless there is some major issue. |
CI failure is Karm/mandrel-integration-tests#290 and is not related to this specific version. |
Thanks! |
Merge upstream changes from
vm-24.1.1
tag.The merge was clean, but there are two open issues for properly testing this branch: