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

Fix reflect ConstantPool bootstrapping issues #18169

Merged
merged 1 commit into from
Sep 21, 2023

Commits on Sep 20, 2023

  1. Fix reflect ConstantPool bootstrapping issues

    We currently perform explicit native registration for
    jdk.internal.reflect.ConstantPool. This occurs after JCL init in VM
    startup. It is possible that ConstantPool will be used in JCL init before
    the natives are registered, this will result in signal 218 since we have
    public JNI stubs as a catch all for these capabilities.
    
    I propose the following:
    
    Step 1) (this PR)
    - introduce a registerNative call in ConstantPool.
    
    Step 2)
    - update the JCL code to use the registerNative() in the static initializer
    of the class, thereby ensuring that the natives are registered before the
    class is used.
    
    Step 3)
    - remove the explicit register native call
    
    With these steps we dont need to do any build coordination between openj9
    and the extension repos.
    
    Signed-off-by: tajila <[email protected]>
    tajila committed Sep 20, 2023
    Configuration menu
    Copy the full SHA
    4b61672 View commit details
    Browse the repository at this point in the history