On 9/26/07, Alexandre Oliva <[EMAIL PROTECTED]> wrote: > On Sep 11, 2007, Mark Mitchell <[EMAIL PROTECTED]> wrote: > > > That's a possibility, but I don't want to commit at this point. We can > > have a look at it when you submit it and decide. However, in general, > > introducing churn for the sake of a feature that will be off by default > > isn't something that I would want to do. The more compartmentalized you > > make it, the better your chances are. > > It's nearly impossible to make the patch compartmentalized, but pretty > much all of the changes would be clearly disabled and no-ops unless > the flag was given in the command line. > > That said, I found out there's still a long way to go before this is > actually a no-op in terms of generated code (other than debug info, > that is), as far as testsuite results, target libraries and other > ports are concerned, so I'm thinking this is very unlikely to make 4.3 > :-(
Can you develop this more in the open to allow contribution, facititate further review and make merging it to 4.4 less pain? It looks like that if the patch is not easy to compartmentalize then a branch would be appropriate, though also patches would be fine. I find myself in a situation where I would need to start doing the same work as you (possibly). Thanks, Richard.
