Re: RFC: semi-automatic hookization

2010-11-20 Thread Ian Lance Taylor
Joern Rennecke writes: > Before I go and make all these target changes & test them, is there at > least agreemwent that this is the right approach, i.e replacing > CUMULATIVE_ARG * > with void *, and splitting up x_rtl into two variables. I don't know how we want to get there, but it seems to me

Re: RFC: semi-automatic hookization

2010-11-19 Thread Nathan Froyd
On Tue, Nov 16, 2010 at 06:23:32AM -0800, Ian Lance Taylor wrote: > Joern Rennecke writes: > > Before I go and make all these target changes & test them, is there at > > least agreemwent that this is the right approach, i.e replacing > > CUMULATIVE_ARG * > > with void *, and splitting up x_rtl int

Re: RFC: semi-automatic hookization

2010-11-16 Thread Joern Rennecke
Quoting Ian Lance Taylor : Joern Rennecke writes: Before I go and make all these target changes & test them, is there at least agreemwent that this is the right approach, i.e replacing CUMULATIVE_ARG * with void *, and splitting up x_rtl into two variables. I don't know how we want to get t

Re: RFC: semi-automatic hookization

2010-11-16 Thread Joern Rennecke
Quoting Ian Lance Taylor : Joern Rennecke writes: Before I go and make all these target changes & test them, is there at least agreemwent that this is the right approach, i.e replacing CUMULATIVE_ARG * with void *, and splitting up x_rtl into two variables. I don't know how we want to get t

Re: RFC: semi-automatic hookization

2010-11-15 Thread Joern Rennecke
target.h and function.h include tm.h, and they got data structure dependencies that are painful to untangle. function.h requires x_rtl to be split into a target-type tainted part and one that can be used in tree optimizers / frontends (via the inline functions in emit-rtl.c). To get rid of t

Re: RFC: semi-automatic hookization

2010-11-15 Thread Joern Rennecke
Quoting Paolo Bonzini : Augmenting libcpp with a new kind of poisoning that only affect preprocessor conditionals would probably make this a lot simpler. If we don't have a wrapper macro, we can just poison the macro. I still have to find out how practical that is, but for now let's assume we

Re: RFC: semi-automatic hookization

2010-11-15 Thread Paolo Bonzini
On 11/15/2010 04:48 PM, Joseph S. Myers wrote: * The macro is tested with #if/#ifdef/#ifndef/#elif in a source file outside of config/ (but including front-end subdirectories). Care is needed in identifying such macros through grep because of backslash-newline line continuations and because it's

Re: RFC: semi-automatic hookization

2010-11-15 Thread Joseph S. Myers
On Mon, 15 Nov 2010, Joern Rennecke wrote: > Quoting "Joseph S. Myers" : > > > On Mon, 15 Nov 2010, Joern Rennecke wrote: > > > > > With 638 macros documented by @defmac, and 475 files that include tm.h , > > > our current approach to hookization is too slow to get the tree optimizers > > > and

Re: RFC: semi-automatic hookization

2010-11-15 Thread Joern Rennecke
Quoting "Joseph S. Myers" : On Mon, 15 Nov 2010, Joern Rennecke wrote: With 638 macros documented by @defmac, and 475 files that include tm.h , our current approach to hookization is too slow to get the tree optimizers and front ends independent of target macros in any useful timeframe. I th

Re: RFC: semi-automatic hookization

2010-11-15 Thread Joseph S. Myers
On Mon, 15 Nov 2010, Joern Rennecke wrote: > With 638 macros documented by @defmac, and 475 files that include tm.h , > our current approach to hookization is too slow to get the tree optimizers > and front ends independent of target macros in any useful timeframe. I think it's perfectly feasible