On Fri, Nov 14, 2014 at 01:16:36PM +0100, Richard Biener wrote:
> > That would be indeed nice (similarly for other stuff that we expect to be
> > undefined on pass boundaries, or expect to be in certain state at pass
> > boundaries; in the former case set before uses, and don't care about what
> > state we leave it in, in the latter case can assume some state first (say 0)
> > and have to put it back into the same state). There are various visited
> > flags and the like, Richard, any ideas what other things might be nice to
> > document?
>
> aux pointers on CFG structures which I believe have to be cleared
> after each pass that uses them (maybe already documented).
>
> Nothing else off the top of my head.
There is at least gimple_plf GF_PLF_{1,2} too, gimple_visited_p, BB_VISITED,
...
Jakub
