summaryrefslogtreecommitdiffstats
path: root/base
diff options
context:
space:
mode:
authorcraig.schlenter@chromium.org <craig.schlenter@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-01-13 19:25:42 +0000
committercraig.schlenter@chromium.org <craig.schlenter@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-01-13 19:25:42 +0000
commitecf52cb820c80a600436aca1a5a72533db32b48d (patch)
tree8548e6bda277f73d26833a0f73696885a5a3ca2a /base
parent001f484f9e86caca78dfb7f17631746ce8e5dbc0 (diff)
downloadchromium_src-ecf52cb820c80a600436aca1a5a72533db32b48d.zip
chromium_src-ecf52cb820c80a600436aca1a5a72533db32b48d.tar.gz
chromium_src-ecf52cb820c80a600436aca1a5a72533db32b48d.tar.bz2
Use no_strict_aliasing=1 by default.
This will turn on -fno-strict-aliasing. There are regular aliasing problems in the codebase and at least one of these was not caught by -Wall -Werror so defaulting to -fno-strict-aliasing seems like a good idea especially given the increased popularity of gcc 4.4 with it's use in karmic, fedora and in chromeos chroot builds et. al. The long term plan is to have some test infrastructure in place that will test 4.4 binaries and to fix the aliasing issues. BUG=28749 Review URL: http://codereview.chromium.org/519034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36151 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base')
0 files changed, 0 insertions, 0 deletions