https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122672
--- Comment #4 from Robin Dapp <rdapp at gcc dot gnu.org> --- (In reply to Yunbo Ni from comment #3) > (In reply to Robin Dapp from comment #2) > > (In reply to Yunbo Ni from comment #1) > > > Cannot reproduce with RISCV64 gcc (trunk) in compiler explorer. I built > > > riscv64-unknown-linux-gnu-gcc based on the latest commit (4e7952b) though. > > > > Do you see the issue with 4e7952b or just with "gcc version 15.1.0 > > (g1b306039a)"? I just tried it but with a few local patches on top and > > cannot reproduce it. > > I built my toolchain from riscv-collab/riscv-gnu-toolchain, and it looks > like their GCC submodule is still pointing to GCC 15.1.0 (1b306039a). So > this is really an issue with the toolchain repo. Sorry about the confusion, > I’ll switch to building GCC directly instead. GCC 16 is not released yet so it's fine to use 15.1. But this means that 15.1 has that bug and we should backport the fix if possible?
