diff options
| author | fischman@chromium.org <fischman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-29 23:35:39 +0000 |
|---|---|---|
| committer | fischman@chromium.org <fischman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-29 23:35:39 +0000 |
| commit | 6211f620d2068c21599633488f752555cb29054a (patch) | |
| tree | f15a9e9250a45a44d333b3fa9a8c4f46173180b9 /base | |
| parent | 34dc645193743944aac8cbf8bf7206a0257d302b (diff) | |
| download | chromium_src-6211f620d2068c21599633488f752555cb29054a.zip chromium_src-6211f620d2068c21599633488f752555cb29054a.tar.gz chromium_src-6211f620d2068c21599633488f752555cb29054a.tar.bz2 | |
build/common.gypi: revert the change to GCC_STRICT_ALIASING:NO because some bots have a too-old xcode.
In particular, rolling chromium_revision in webrtc from 211877 to 211878 broke
the webrtc mac Release bots:
http://build.chromium.org/p/client.webrtc/builders/Mac64%20Release/builds/296
http://build.chromium.org/p/client.webrtc/builders/Mac32%20Release/builds/312
http://build.chromium.org/p/client.webrtc/builders/Mac%20Asan/builds/304
The breakage did not repro on the webrtc trybots which use ninja (filed
https://code.google.com/p/webrtc/issues/detail?id=2135 to fix the inconsistency)
nor did it repro in an xcode build on my MBP (4.6.3). My theory is that the
xcode on the bots (e.g. vm674-m3) is too old (4.5.1).
R=thakis@chromium.org
Review URL: https://codereview.chromium.org/20666002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214260 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base')
0 files changed, 0 insertions, 0 deletions