CALL_EXPR representation changes coming; need patch reviewer(s)

[Mike Stump]

On Feb 8, 2007, at 3:27 PM, Sandra Loosemore wrote:
> Once the patch is approved, we will probably need to ask for a  
> check-in window for the final merge and commit, as described in
>
> http://gcc.gnu.org/ml/gcc/2006-09/msg00454.html

Hum, what rule for mainline were you thinking of?  A no branch  
merging and no changes to any CALL_EXPR code seem reasonable.  I'd  
hope that you'd not need a complete lock down on any changes rule.   
If you're thinking about a general no changes lock down, I'd counter  
propose that you just, up-port to mainline, get that reviewed and  
approved, svn up the tree, resolve conflicts, build, svn ci, svn up  
and then do one last build.  The cost to others is then just about 0,  
unless there was some lagging integration work caused by work checked  
in before your second to last build and the last build.