Merge upstream changes into Mandrel 23.1 release branch #787
Conversation
(cherry picked from commit c6bdbb6)
(cherry picked from commit 261dd42)
(cherry picked from commit 0c518c7)
Fix build with --no-jlinking
Don't allow null values to be passed to the `register` method of `RuntimeJNIAccess` and `RuntimeReflection`. Since these are public APIs GraalVM should either handle null values (by ignoring them in this case) or throw a `NullPointerException` before creating an asynchronous task to perform the registration in the analysis, which then results in `NullPointerException`s being thrown later when it's no longer possible to understand where the null value originate from. (cherry picked from commit e6c12dd)
(cherry picked from commit d621dbd)
Not before the register methods, which can miss cases, nor later on in a runnable. (cherry picked from commit f94551a)
(cherry picked from commit d996f32)
(cherry picked from commit 0ba6cc2)
(cherry picked from commit c949f3e)
Partial backport of [GR-48529] Use the API flag in the init hint
…xes-backport Backport: [GR-49816] Throw exception for null pointers passed to RuntimeJNIAccess / RuntimeReflection register methods
This is a no-op change, but makes downstream Mandrel 23.1 be in sync with the upstream community repo. It makes it easier to spot any downstream only patches if the diff to upstream is minimal.
oracle-contributor-agreement
bot
added
the
OCA Verified
|
FYI, the remainder of the diff to the upstream repo is (all are Mandrel related, so I consider this the minimal diff): |
I agree, the only things we need to apply upstream are the checkout github action version bump and the version bump of GraalVM itself. |
OK. |
Done with these: |
A trivial merge which only includes the whitespace change discussed here. Otherwise, this would be an empty diff.
After this merge only Mandrel-specific diffs are present in the release tree which aren't in the
upstream community-jdk21u repo.