[Bug target/110478] RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110478 --- Comment #7 from Bin Meng --- Any update about this issue?

[Bug target/110478] RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110478 --- Comment #6 from Bin Meng --- While I am figuring out the build failure, Palmer or Kito, are you able to reproduce this libgcc bug with zicsr on the GCC HEAD?

[Bug target/110478] RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110478 --- Comment #4 from Bin Meng --- I can't get the build to pass with the same configure scripts on current GCC HEAD :( --host=x86_64-linux-gnu --build=aarch64-linux --target=riscv64-linux --enable-targets=all --prefix=/home/arnd/cross/x86_64/gcc

[Bug target/110478] RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110478 --- Comment #2 from Bin Meng --- I am not sure I understand your comments. Are you saying that this behavior of "zicsr" libgcc path in the multilib configuration is intentional?

[Bug driver/110478] New: RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110478 Bug ID: 110478 Summary: RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: