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

Get rid of AIX linker option: -bnorwexec #162

Open
zl-wang opened this issue May 29, 2024 · 1 comment
Open

Get rid of AIX linker option: -bnorwexec #162

zl-wang opened this issue May 29, 2024 · 1 comment

Comments

@zl-wang
Copy link
Contributor

zl-wang commented May 29, 2024

High-level: this linker option is oxymoronic with JIT environment (where executable code are generated on the fly anyway).

At least for the time being before we figured out why default codeCache is allocated through malloc (instead of mmap or shmget, for which that linker option appeared to have no effect by my tests).

Even after we figured it out eventually, it is a legitimate question what value this option provides for JIT environment.

@zl-wang
Copy link
Contributor Author

zl-wang commented May 29, 2024

In jdk21, this also has effect on FFI thunks (which are not generated in JIT codecache).

zl-wang added a commit to zl-wang/openj9-openjdk-jdk22 that referenced this issue May 29, 2024
High-level: this linker option is oxymoronic with JIT environment (where executable code are generated on the fly anyway).

At least for the time being before we figured out why default codeCache is allocated through malloc (instead of mmap or shmget, for which that linker option appeared to have no effect by my tests).

Even after we figured it out eventually, it is a legitimate question what value this option provides for JIT environment.

this also has effect on FFI thunks (which are not generated in JIT codecache).

Issue ibmruntimes/openj9-openjdk-jdk21#162
zl-wang added a commit to zl-wang/openj9-openjdk-jdk21 that referenced this issue May 29, 2024
High-level: this linker option is oxymoronic with JIT environment (where executable code are generated on the fly anyway).

At least for the time being before we figured out why default codeCache is allocated through malloc (instead of mmap or shmget, for which that linker option appeared to have no effect by my tests).

Even after we figured it out eventually, it is a legitimate question what value this option provides for JIT environment.

this also has effect on FFI thunks (which are not generated in JIT codecache).

Issue ibmruntimes#162
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant