-
Notifications
You must be signed in to change notification settings - Fork 754
Remove _magic_ constant J9_FFI_DOWNCALL_HEAP_ARGUMENT_ID
#19005
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
Comments
FYI @ChengJin01. |
Instead of relying on |
The changes aim to avoid the conflicts of the native address imposed by users by check the existence of the heap base to determine whether a heap array rather than a native array is passed down to native. Fixes: eclipse-openj9#19005 Signed-off-by: ChengJin01 <jincheng@ca.ibm.com>
The changes aim to avoid the conflicts of the native address imposed by users by check the existence of the heap base to determine whether a heap array rather than a native array is passed down to native. Fixes: eclipse-openj9#19005 Signed-off-by: ChengJin01 <jincheng@ca.ibm.com>
The changes aim to avoid the conflicts of the native address imposed by users by check the existence of the heap base to determine whether a heap array rather than a native array is passed down to native. Fixes: eclipse-openj9#19005 Signed-off-by: ChengJin01 <jincheng@ca.ibm.com>
The changes aim to avoid the conflicts of the native address imposed by users by check the existence of the heap base to determine whether a heap array rather than a native array is passed down to native. Fixes: eclipse-openj9#19005 Signed-off-by: ChengJin01 <jincheng@ca.ibm.com>
The changes aim to avoid the conflicts of the native address imposed by users by check the existence of the heap base to determine whether a heap array rather than a native array is passed down to native. Fixes: eclipse-openj9#19005 Signed-off-by: ChengJin01 <jincheng@ca.ibm.com>
The changes aim to avoid the conflicts of the native address imposed by users by check the existence of the heap base to determine whether a heap array rather than a native array is passed down to native. Fixes: eclipse-openj9#19005 Signed-off-by: ChengJin01 <jincheng@ca.ibm.com>
The changes aim to avoid the conflicts of the native address imposed by users by check the existence of the heap base to determine whether a heap array rather than a native array is passed down to native. Fixes: eclipse-openj9#19005 Signed-off-by: ChengJin01 <jincheng@ca.ibm.com>
The changes aim to avoid the conflicts of the native address imposed by users by check the existence of the heap base to determine whether a heap array rather than a native array is passed down to native. Fixes: eclipse-openj9#19005 Signed-off-by: ChengJin01 <jincheng@ca.ibm.com>
The changes aim to avoid the conflicts of the native address imposed by users by check the existence of the heap base to determine whether a heap array rather than a native array is passed down to native. Fixes: eclipse-openj9#19005 Signed-off-by: ChengJin01 <jincheng@ca.ibm.com>
J9_FFI_DOWNCALL_HEAP_ARGUMENT_ID
was originally0x1
, but changed to0xFFFFFFFFFFFFFFFF
in #19002. No matter what value is chosen, it's possible it conflicts with application intent. As I suggested, I think we should use an out-of-band channel to distinguish parameters that should point within the heap from other parameters.The text was updated successfully, but these errors were encountered: