-
Notifications
You must be signed in to change notification settings - Fork 5.2k
fix the regs conflicts within the addResolution for LoongArch64 and RISC-V.
#86294
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
Conversation
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsThis PR is part of the issue #69705 to amend the LA's port. The LoongArch64 is very different with the AArch64 and AMD64. If insert move before the branch just liking AArch64 or AMD64, there maybe conflicts.
|
bf90be2 to
cf26543
Compare
|
Hi, @jakobbotsch |
|
@shushanhf This should be fixed in LSRA instead. It is what this TODO is about: runtime/src/coreclr/jit/lsra.cpp Lines 8172 to 8176 in 7486bde
|
OK, Thanks. |
cf26543 to
7caaa18
Compare
addResolution.addResolution for LoongArch64 and RISC-V.
0300378 to
4649630
Compare
4649630 to
4dcd720
Compare
4b62368 to
c14b3fc
Compare
|
Test failure is #86233 that is known by build analysis. |
This PR is part of the issue #69705 to amend the LA's port.
The LoongArch64 is very different with the AArch64 and AMD64.
If insert move before the branch just liking AArch64 or AMD64, there maybe conflicts.
This should be also valid for RISCV64. cc @clamp03