https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94538
--- Comment #13 from Wilco <wilco at gcc dot gnu.org> --- (In reply to Christophe Lyon from comment #12) > I've posted a patch to fix the regression for your f3() examples: > https://gcc.gnu.org/pipermail/gcc-patches/2020-April/543993.html Yes that improves some of the examples, but I still see regressions on m0 for eg. -1 or 511. The splitter must have the right priority or it will continue to cause regressions. That means placing it around line 790 after the existing movsi splitters.