On Fri, Sep 6, 2013 at 5:21 PM, Andrew MacLeod wrote: >> hackery in some headers will suddenly break (that is, change outcome) >> if you include for example >> tm.h before or after it. >> > these would be really good to identify and fix, if possible. (surely they > can be fixed.. :-) if they cant be fixed for whatever reason, we ought to > protect them with some mechanism.. ie assert that tm.h either has or has not > been included before hand... whichever way is required. At least then we > get an error if it changes. > > Do you know of any of the top of your head?
sched-int.h comes to mind as an example I fixed recently (it needs INSN_SCHEDULING from insn-attr.h. But these cases are hard to discover. Usually you simply run into them while trying to re-arrange the #includes of a .c file. Ciao! Steven
