-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Proof of concept for preserving more linkage errors #6755
Proof of concept for preserving more linkage errors #6755
Conversation
Thanks for the PoC. Could you provide an example where this is useful? How many additional LinkageErrors are collected through this for a helloworld and/or Quarkus app? |
This is useful when a type is not found while parsing bytecode (e.g. Without it we just get an unresolved type exception without the Reproducer
OutputWithout this PR
With this PR
I will get some numbers and get back to you :) |
Which makes sense, since a |
@fniephaus this (unpolished) PR demonstrates how you could extend #6753 to preserve even more linkage errors and further improve error reporting. However, as mentioned in #6507 (comment) we will still need some JVMCI changes to handle these properly.
It looks like not every class loading goes through https://github.com/oracle/graal/pull/6753/files#diff-05fc37f93d8c3289b812fb9f571b8236a3c18cf5310ca34303bcbba16ba3f0eaL823