https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87763
--- Comment #14 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- I've checked cvtf_1.c generated code and I don't see additional fmov anymore. I guess it was fixed by an ira-costs.c change (a special consideration of moves containing hard regs). I think this PR is resolved (although the change resulted in a new PR 88560 but it is a different story). If we want to improve the generated code size, it would be better to find a small testcase from SPEC2006 showing what is wrong. I understand it is a hard work but otherwise we could only speculate what is going wrongly. I don't think that reverting the combiner change would be a solution.
