[LoongArch64] Apply fixes for coreclr-interp on linux-loongarch64.#129887
[LoongArch64] Apply fixes for coreclr-interp on linux-loongarch64.#129887LuckyXu-HF wants to merge 1 commit into
Conversation
…like issue#127860.
|
Tagging subscribers to this area: @agocke |
|
LA64 also hit the same issue like #127860 : Fixed: InterpreterTester.sh PASS |
| // Note that the regNum == 0 only occurs under interpreter. | ||
| assert(regNum == 3 || 22 == regNum || 0 == regNum); | ||
| #elif defined(TARGET_RISCV64) | ||
| assert(regNum == 2 || 8 == regNum); |
There was a problem hiding this comment.
Hi @am11 , does riscv64 also need to modify here? I'm curious why riscv64 can pass the assertion here.
There was a problem hiding this comment.
@LuckyXu-HF, tests were passing in May #127919 (comment) so I'm not sure why it wasn't failing if you think it's needed there. Are you running the same test command (with Debug configuration), I can test with latest main branch.
There was a problem hiding this comment.
@am11 Do you test the CoreRoot by qemu-chroot for LoongArch?
There was a problem hiding this comment.
@LuckyXu-HF, tests were passing in May #127919 (comment) so I'm not sure why it wasn't failing if you think it's needed there. Are you running the same test command (with Debug configuration), I can test with latest main branch.
Yes, I'm running the same test command with Debug configuration based on commit 3d40d73, both linux-loongarch64/linux-arm64 will set the regNum 0 by
runtime/src/coreclr/interpreter/compiler.cpp
Line 1591 in 3d40d73
And big thanks to your PR #127909 we can cross-build the test artifacts faster! The cross-build artifacts CoreRoot tests running on native machine results is as good as those from native builds and tests.
But maybe the cross environment cannot fully simulate the actual hardware, CoreRoot tests running on cross-env is not as good as native machine tests.
Does community CI testing entirely based on real hardware? Could you please help to give us some advice? Thank you very much!
Align PR#127919 to fix the InterpreterTester.sh failed like issue:#127860 on LA64.