[GR-70612] Propagate exceptions faithfully from HotSpot to libgraal when thrown in a canCallJava scope #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a problem in the translation of exceptions from HotSpot to libgraal that was exposed now that annotation parsing is done in libgraal:
The problem was 2-fold:
CompilerThreadCanCallJavaso that it will translate pending HotSpot -> libgraal exceptions before closing a scope that allows such calls.Class.forNameis neutered in libgraal. Rather than reviving this support, I opted to replace the use ofClass.forNamewith an explicit list of supported exception types as there are only a few core exceptions that need type-preserving translation in libgraal.I tested this in Graal with this patch:
and by running Test.java (in fish shell):
The output is: