https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117467
--- Comment #18 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jeff Law <l...@gcc.gnu.org>: https://gcc.gnu.org/g:7d3aec2a832ef47be547d9426187562e4548bae6 commit r15-7916-g7d3aec2a832ef47be547d9426187562e4548bae6 Author: Jeff Law <j...@ventanamicro.com> Date: Sun Mar 9 14:25:37 2025 -0600 [rtl-optimization/117467] Mark FP destinations as dead The next step in improving ext-dce is to clean up a minor wart in the set/clobber handling code. In that code the safe thing to do is to not process a destination at all. That will leave bits set in the live bitmaps for objects that may no longer be live. Of course with extraneous bits set we use more memory and do more work managing the bitmaps, but it's safe from a code correctness standpoint. One case that is slipping through that we need to fix is scalar fp destinations. Essentially the code never tried to handle those and as a result would leave those entities live and bubble them up through the CFG. In the testcase at hand this takes us from ~10k live objects at entry to ~4k live objects at entry. Time spent in ext-dce goes from 2.14s to .64s. Bootstrapped and regression tested on x86_64. PR rtl-optimization/117467 gcc/ * ext-dce.cc (ext_dce_process_sets): Handle FP destinations better.
