https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107323
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- OK, so I think I found an alternate fix for PR94125 that makes more sense. When deciding to merge SCCs rather than breaking them we have to make sure to _not_ ignore the alias edges in those SCCs when doing the final SCC discovery so postorder info correctly reflects this merging. That allows us to remove the save/restore of the wrong postorder (just removing that reproduces PR94125 on the gcc 10 branch again), fixing this bug.
