On Wed, 10 Jan 2024, Richard Sandiford wrote: > Just a note that, following discussion on IRC, I'll pull this for > GCC 14 and resubmit for GCC 15. > > There was also pushback on IRC about making the pass opt-in. > Enabling it for x86_64 would mean fixing RPAD to use a representation > that is more robust against recombination, but as you can imagine, it's > kind-of difficult for me to justify spending significant time fixing an > issue in the x86_64 port. Jeff's testing suggested that there are also > latent issues in the older, less maintained ports. > > So to get an idea for expectations: would it be a requirement that a > GCC 15 submission is enabled unconditionally and all known issues in > the ports fixed?
Can you open a bugreport with the issue in RPAD, maybe outlining what would need to be done? I think x86 maintainers could opt to disable the pass - so it would be opt-out. It's reasonable to expect them to fix the backend given there's nothing really wrong with the new pass, it just does something that wasn't done before at that point? Richard.
