A new version is on the list ( https://gcc.gnu.org/pipermail/gcc-patches/2025-November/701395.html).
It turns out that I hadn't applied some changes before testing, so this was OK on RISC-V too. The new version re-enables it on all targets. Konstantinos. On Fri, Nov 14, 2025 at 7:55 PM Jeff Law <[email protected]> wrote: > > > On 11/14/25 10:19 AM, Andrew Pinski wrote: > > > > > I am not sure this is a good idea if there is a known failure on some > > targets to enable it on other targets by default. > > Plus there is no analysis of the bootstrap failure to say if this is a > > bug in the backend or in the pass. > > If this was the beginning of stage1 rather than the end, it would have > > been better as it means we have much more time to debug what is going > > on. > > Do you have a hint where the bug might be with respect to the riscv > failure? > Totally agreed. This pass has worked on RISC-V since its inception (in > fact issues with code generation on RISC-V were a major motivator behind > this pass), so if it's failing on RISC-V with this patch now we really > need to understand why. > > > Jeff >
