> The un-combining thing around line 2800 is somewhat of a kludge and I > wouldn't be surprised if there were other fallouts. But your change is > clearly correct and looks relatively safe, so OK for trunk and 4.6 branch > after full testing.
I overlooked something though: it might be possible for combine_instructions to try to combine i2 again if the previous combination fails (if it succeeds, i1 is deleted so this is OK) so the stall LOG_LINKS could be problematic. That's why LOG_LINKS (i2) needs to SUBST-ituted like the two lines just above. -- Eric Botcazou
