Skip to content
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

2024-03-27 backports 17 sync #707

Merged
merged 32 commits into from
Mar 27, 2024

Conversation

zakkak
Copy link
Collaborator

@zakkak zakkak commented Mar 27, 2024

Sync with upstream https://github.com/graalvm/graalvm-for-jdk17-community-backports/

  • clean deploy jobs using unsupported JDK
  • clean gate jobs using jdk 20 on truffle
  • clean gate jobs using jdk 20 on compiler
  • clean gate jobs using jdk 20 on VM
  • clean gate jobs using jdk 20 on sulong
  • clean gate jobs using jdk 20 on espresso
  • clean gate jobs using jdk 20 on wasm
  • additional fixes
  • clean ruby deploy gates
  • Remove aload -> getfield optimization from BytecodeParser
  • BytecodeParser: Do not pop values from FrameState before resolving types/fields
  • BytecodeParser: add comment explaining removal of checks in handleUnresolvedNewArray
  • correct gate name resolution
  • [GR-52464] Backport to 23.0: Upgrading the underlying Node.js to version 18.19.1.
  • [GR-52618] Improve uncaught exception handler and error handling in CEntryPointSnippets.initializeIsolate().
  • [GR-52618] Add option ImplicitExceptionWithoutStacktraceIsFatal.
  • [GR-52615] Improve a code installation error message.
  • Build GraalVM on Big Sur
  • Revert "ci: disable darwin-amd64 on JDK latest [GR-49652]"
  • Add new darwin-aarch64 gates back
  • Allow sulong gate to run on big sur
  • Add a comment about the usage of exclusion to get Big Sur or above
  • sync CI
  • Fix for birth time support-ing JDKs
  • update to jvmci-23.0-b34

elkorchi and others added 30 commits February 19, 2024 15:47
…pes/fields

If, during handling of an instruction, we come across an unresolved type/field, we generate an unconditional deoptimization. In such cases we should maintain the values that are present on the stack intact.
However, the `handleUnresolvedX` functions in BytecodeParser encouraged popping values from the stack, even though the obtained values were never used. This PR removes ValueNode parameters from `handleUnresolvedX` functions and reorders some function calls to ensure that no values are popped from a FrameState's stack until we're certain we won't emit a deopt.

(cherry picked from commit f4d0085)
…th incorrect stack size.

PullRequest: graal/17094
Ensure we don't use older macos versions

(cherry picked from commit b7718e9)
This reverts commit 6560ce2.

(cherry picked from commit c798fb4)
(cherry picked from commit e0ac1fa)
(cherry picked from commit 421e12a)
(cherry picked from commit b26611762139f1b0858079d4860d41d356accf75)
PullRequest: graal/17041
@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Mar 27, 2024
@zakkak zakkak merged commit eb5b5e0 into graalvm:mandrel/23.0 Mar 27, 2024
67 checks passed
@zakkak zakkak deleted the 2024-03-27-backports-17-sync branch March 27, 2024 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.