Add max optimization flag to v8 build flag, chrome will use less optimization as default soon.

Add max optimization flag to v8 build flag, chrome will use less optimization as default soon.
Committed: http://code.google.com/p/v8/source/detail?r=10283

[danno, 2011-12-21 07:27:39]

lgtm

[Sigurður Ásgeirsson, 2011-12-21 14:16:06]

http://codereview.chromium.org/9017004/diff/1/build/common.gypi
File build/common.gypi (right):

http://codereview.chromium.org/9017004/diff/1/build/common.gypi#newcode90
build/common.gypi:90: 'optimize': 'max',
This is a little indiscriminate, I'd very much prefer that we do this
per-target. As-is, we'll end up building every target that includes this file
with WPO, and WPO consumes CPU and memory superlinear to the input size.
You really don't want to slow down the official build by WPO-optimizing your
test and misc executables.

[Sigurður Ásgeirsson, 2011-12-21 14:38:46]

I just checked out ToT, and this change doesn't enable WPO optimizations for V8
targets.
Please do this on a per-target basis. From looking at the targets Chrome depends
on, you probably only want to do this for v8_base in
http://v8.googlecode.com/svn/branches/bleeding_edge/tools/gyp/v8.gyp.
There's no reason to enable WPO for targets that contain code that runs very
seldom...