-
Notifications
You must be signed in to change notification settings - Fork 733
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
Add Relocation Error Codes #14893
Add Relocation Error Codes #14893
Conversation
…Relocations It is possible for a few different exceptions to get thrown during relocation. This commit adds catch block for some known exceptions so that the appropriate compilation error code can be set. Signed-off-by: Irwin D'Souza <[email protected]>
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.
Overall it looks good. Only a couple of nitpicks
jenkins test sanity all jdk17 |
Of course there's a build break on windows... Reading up online, it seems the error can happen because the enum's already defined elsewhere. I think it's I guess I'll have to rename the |
|
jenkins test sanity win jdk17 |
I was gonna just rename |
Converting to draft until I sort this all out. |
Add error codes for all the various relocation errors that can occur. Signed-off-by: Irwin D'Souza <[email protected]>
The generic compilation error code will be used in places that need to determine what to do next based on the compilation failure. This is common across most relocation failures. Therefore, it is best to have a generic error code for this purpose, and use the relocation error code for RAS purposes. Signed-off-by: Irwin D'Souza <[email protected]>
Update the relocation infrastructure to return well defined relocation error codes rather than 0, -1, or a generic compilation error code. Signed-off-by: Irwin D'Souza <[email protected]>
The existing logic added a SCC hint for validation failures; this should be updated to use the relocation error codes. This not only simplifies the code, but also will now include several validation failures that were missed. Signed-off-by: Irwin D'Souza <[email protected]>
An AOT load does not use the SharedCacheVM front end. Therefore, the compilation failure line in the vlog did not print out whether the compilation was a failed AOT load. This commit fixes this by passing in the TR_MethodToBeCompiled entry, which can be used to determine whether the compile was an AOT load or not. Signed-off-by: Irwin D'Souza <[email protected]>
Signed-off-by: Irwin D'Souza <[email protected]>
Signed-off-by: Irwin D'Souza <[email protected]>
Apparently |
jenkins test sanity win jdk17 |
Ready for final review @mpirvu |
jenkins compile all jdk17 |
jenkins test sanity.functional+aot all jdk17 |
AIX failure
is a known issue; see #14894 (comment) and #14943. AArch64 failure
is due to #13577. |
Merging since the two tests that are failing are not due to this PR. |
AOT load
if the failed compile was an AOT load