Commit a21de68c authored by maruel@chromium.org's avatar maruel@chromium.org

Revert r113657 "win_release_OmitFramePointers=0 must explicitly pass /Oy-"

We are suspecting this has side effects on official builds.

If so, this is a configuration error. Trying out to be sure.

TBR=timurrrr@chromium.org
BUG=
TEST=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114251 0039d316-1c4b-4281-b951-d872f2087c98
parent 3dd18d02
...@@ -1493,12 +1493,6 @@ ...@@ -1493,12 +1493,6 @@
}], }],
['win_release_OmitFramePointers==0', { ['win_release_OmitFramePointers==0', {
'OmitFramePointers': 'false', 'OmitFramePointers': 'false',
# The above is not sufficient (http://crbug.com/106711): it
# simply eliminates an explicit "/Oy", but both /O2 and /Ox
# perform FPO regardless, so we must explicitly disable.
# We still want the false setting above to avoid having
# "/Oy /Oy-" and warnings about overriding.
'AdditionalOptions': ['/Oy-'],
}], }],
], ],
}, },
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment