On Wed, Nov 24, 2010 at 1:56 PM, Joern Rennecke <amyl...@spamcop.net> wrote: > Quoting Richard Guenther <richard.guent...@gmail.com>: > >> Well. Some things really ought to stay as macros. You can always >> error out if a multi-target compiler would have conflicts there at >> configure time. > > So what are we going to do about all the tree optimizers and frontends that > use BITS_PER_UNIT?
Tree optimizers are fine to use target macros/hooks, and I expect use will grow, not shrink. > Should they all include tm.h, with the hazard that more specific > macros creep in? > Or do we want to put this in a separate header file? I don't have a very clear picture of where we want to go with all the hookization. And I've decided to postpone any investigation until more macros are converted (where it makes sense to). Richard.
