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

☂️ Consider making certain JNI routines leaf functions #1106

Open
11 tasks
HosseinYousefi opened this issue Apr 26, 2024 · 0 comments
Open
11 tasks

☂️ Consider making certain JNI routines leaf functions #1106

HosseinYousefi opened this issue Apr 26, 2024 · 0 comments

Comments

@HosseinYousefi
Copy link
Member

For some of the routines, we can generate both the normal and the leaf versions, and call each one depending on the situation. For example Set<PrimitiveType>ArrayRegion could be fast depending on the length of the region, maybe it makes sense to conditionally call one or the other based on this.

Candidates:

For jnigen, users should be able to specify if a method is leaf or not, this can be done as a part of jnigen transformation. However simply:

  • Getting a field
  • Setting a field
    Can be safely turned into leaf calls.

cc/ @dcharkes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant