Is there an idiom for target-specific back end code to ask the pass
manager if a particular pass (e.g., "split1") has already run?
I have some nios2 addressing mode improvement patches in the works that
depend on deferring splitting of some complex address forms until after
cse and fwprop, instead of during expand. Once "split1" has run,
TARGET_LEGITIMATE_ADDRESS_P shouldn't consider those address forms valid
any more. For now I've solved this problem by adding a target-specific
pass immediately after "split1" that does nothing but set a flag, but
that seems kind of hacky. If I can get at the information from the pass
manager's public interface, that seems like a better solution, but I've
gotten rather lost in that code. :-(
I suppose another alternative is adding a split1_completed variable akin
to reload_completed, but I'm hesitant to touch target-independent code
for things that aren't generally useful.
Any suggestions/recommendations?
-Sandra
