https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120182
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- In fact it's the gid assignment: **scanning insn=17 mem: (const_int 2654208 [0x288000]) after canon_rtx address: (const_int 2654208 [0x288000]) gid=1 offset=0 processing const base store gid=1[0..1) mems_found = 1, cannot_delete = false **scanning insn=19 mem: (const_int 2654209 [0x288001]) after canon_rtx address: (const_int 2654209 [0x288001]) gid=2 offset=0 processing const base store gid=2[0..1) ... **scanning insn=33 mem: (const_int 2654208 [0x288000]) after canon_rtx address: (const_int 2654208 [0x288000]) gid=1 offset=0 processing const load gid=1[0..8) removing from active insn=17 has store mems_found = 0, cannot_delete = true