Loongarch/riscV: ThreadLocal optimization during JIT should detect static/dynamic resolver

[kunalspathak]

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

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[jkotas]

cc @shushanhf @dotnet/samsung

[dotnet-policy-service]

This issue has been marked needs-author-action and may be missing some important information.

[JulieLeeMSFT]

Ping @shushanhf, @dotnet/samsung if you can look into this. RC1 snap is 8/14.

[shushanhf]

Ping @shushanhf, @dotnet/samsung if you can look into this. RC1 snap is 8/14.

@kunalspathak @JulieLeeMSFT
The #104408 is still in progress. Do you merge the #104408 within the RC1? And should I reference the #104408 for LA64？

[davidwrighton]

@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.