On Tue, Mar 23, 2010 at 2:24 PM, wrote:
> Just a thought.. but instead of a new flag, what if we redefined
> "aggressive optimizations" to mean just GFlow, since all the other
> optimizations have a lot of miles on them now. What do you think?
I like the idea of updating the aggressive optimiz
Just a thought.. but instead of a new flag, what if we redefined
"aggressive optimizations" to mean just GFlow, since all the other
optimizations have a lot of miles on them now. What do you think?
http://gwt-code-reviews.appspot.com/260801/show
--
http://groups.google.com/group/Google-Web-Tool
Bob, can you review this little patch?
It adds a flag -XdisableGflow that does exactly what it sounds like.
This would provide a safety valve in case there are any problems that
arise from the new gflow optimizer.
In a month or so we could reevaluate whether we need to keep the flag or
not.
htt
