RFC: peephole vs RTX_FRAME_RELATED_P

Tue Jan 3 06:36:00 GMT 2006

On Mon, 2 Jan 2006, Ian Lance Taylor wrote:
> I wouldn't expect to see any insns with RTX_FRAME_RELATED_P set before
> the prologue and epilogue are threaded in the flow2 pass. So combine
> shouldn't be an issue. And flow2 calls split_all_insns before the
> prologue and epilogue insns are threaded. When did the bogus split
> happen?

Huh, I emitted RTL prologue insns that were themselves
candidates for splitting (without any transformations).
I thought the same could happen for RTL transformations but it
seems peephole2 (and stack adjustments, but that's not
applicable to CRIS) was the only "real" candidate.
So, there's just an undocumented implicit requirement that
nothing emitted as RTL prologue (accidentally) matches a
splitter.
brgds, H-P