With this change, each target can select an optimization level for Windows official...
commit2212d27f2cc41983901f45299cda82d704c76e82
authorsiggi@chromium.org <siggi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 20 Dec 2011 21:37:37 +0000 (20 21:37 +0000)
committersiggi@chromium.org <siggi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 20 Dec 2011 21:37:37 +0000 (20 21:37 +0000)
treefd93ccd2a78bf29937cd08d79bdb36d6f64378d3
parent91f0305ba68709d19b3ac85ffa67a0dc5525503e
With this change, each target can select an optimization level for Windows official builds by setting a variable name "optimize" to one of three possible values:
- "size"; optimizes for minimal code size, the default.
- "speed"; optimizes for speed over code size.
- "max"; turns on link time code generation and whole
   program optimization, which is very expensive and should
   be used sparingly.

Note that this change by itself lowers the optimization level to "size" for all targets. Separate changes to the V8 and WebKit repos will be needed to bring up their optimization levels to WPO.

BUG=108167
TEST=

Review URL: http://codereview.chromium.org/8983002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@115187 0039d316-1c4b-4281-b951-d872f2087c98
build/common.gypi
build/internal/release_defaults.gypi
build/internal/release_impl.gypi
build/internal/release_impl_official.gypi