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

CoreCLR Interpreter - preventing executable code generation at runtime #112743

Open
8 tasks
janvorli opened this issue Feb 20, 2025 · 1 comment
Open
8 tasks

Comments

@janvorli
Copy link
Member

Currently, CoreCLR generates some executable code at runtime besides the JITted code. This work stream will provide alternative approaches for platforms that don't allow runtime executable code generation.

M1

M2

  • Alternative to VSD dispatch stubs
  • Alternative to the way fixup and stub precodes and call counting stubs are generated.

M3

  • Alternative GC write barrier
  • Alternative to the ThisPtrRetBufPrecode
  • Alternative to the UMEntryThunk

M4

  • Alternative to the DynamicHelpers used by the R2R code

M5

  • Alternative to ShuffleThunks + Non-IL based Unboxing stubs
  • Modify debugger code to work properly with all the changes made to prevent executable code generation at runtime.
@janvorli janvorli added this to the 10.0.0 milestone Feb 20, 2025
@janvorli janvorli self-assigned this Feb 20, 2025
Copy link
Contributor

Tagging subscribers to this area: @dotnet/interop-contrib
See info in area-owners.md if you want to be subscribed.

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

No branches or pull requests

2 participants