-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Loongarch/riscV: ThreadLocal optimization during JIT should detect static/dynamic resolver #104518
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
cc @shushanhf @dotnet/samsung |
This issue has been marked |
Ping @shushanhf, @dotnet/samsung if you can look into this. RC1 snap is 8/14. |
@kunalspathak @JulieLeeMSFT |
@shushanhf @dotnet/samsung This is now fixed as of the merge of PR #106052. You should be able to write a followup PR for each of your architectures that fixes this problem for your scenarios. |
OK,Thanks |
Fixed by #106250 . |
#106250 fixed this for Loongarch. We still need a fix for RiscV. |
@tomeksowi Could you fix this for RISC-V? Thank you. |
@tomeksowi If you can't, please assign to a member in SRPOL. |
OK, I'll take it. |
Update: I got an implementation for RISC-V but now corerun is crashing:
where reloc type 0x0c is TLSDESC on RISC-V ELF. Not sure if that has something to do with tlsdesc being fairly recent addition to RISC-V toolchain. @dotnet/samsung If anyone has an idea, I'd be grateful. |
The JIT code today assume that static resolver will give us a small offset that we embed in JIT. However, with dynamic resolver, the offset returned can that be of current thread, and embedding it in JIT code might be problematic. We are addressing the problem for arm64 in #104408, but might have to do similar thing (after validation) for loongarch/riscv
The text was updated successfully, but these errors were encountered: