|
|
Chromium Code Reviews|
Created:
6 years, 1 month ago by Chris Masone Modified:
6 years, 1 month ago CC:
chromium-reviews Base URL:
https://chromium.googlesource.com/chromium/src.git@master Project:
chromium Visibility:
Public. |
DescriptionDisable -Wextra for all toolchains.
On clang, this flag is a no-op, and Blink code has a long way to go to be
clean with respect to these warnings on GCC toolchains. The GYP build has
never had -Wextra set, so let's just make GN in line with that.
BUG=424334
TEST=try bots
TBR=brettw
Committed: https://crrev.com/c9aa95f7873dc969f35cded9b4f2e2692af91b18
Cr-Commit-Position: refs/heads/master@{#302693}
Patch Set 1 #
Total comments: 1
Patch Set 2 : switch to disabling -Wextra altogether #
Total comments: 2
Patch Set 3 : Add -Wno-type-limits to GYP build #
Total comments: 1
Patch Set 4 : get rid of -Wno-type-limits altogether #Messages
Total messages: 21 (3 generated)
cmasone@chromium.org changed reviewers: + brettw@chromium.org, thakis@chromium.org
cmasone@chromium.org changed reviewers: + scottmg@chromium.org
Brett, can you give this a look?
https://codereview.chromium.org/692313002/diff/1/build/config/compiler/BUILD.gn File build/config/compiler/BUILD.gn (right): https://codereview.chromium.org/692313002/diff/1/build/config/compiler/BUILD.... build/config/compiler/BUILD.gn:532: "-Wextra", I'd just remove this. -Wextra is a no-op in clang, and it's removed on all non-clang platforms in gyp: https://code.google.com/p/chromium/codesearch#chromium/src/build/common.gypi&...
Is this in sync with the GYP build?
As Nico says, the GYP build doesn't set -Wextra at all, and scottmg said in email that it was more-or-less aspirational. Also, Blink code seems to have a long way to go to be clean WRT -Wextra, so I'm just going to take it out. /sadpanda.
OK, PTAL
https://codereview.chromium.org/692313002/diff/20001/build/config/compiler/BU... File build/config/compiler/BUILD.gn (right): https://codereview.chromium.org/692313002/diff/20001/build/config/compiler/BU... build/config/compiler/BUILD.gn:754: "-Wno-type-limits", If you want to keep this, I'd add it to the gyp build too. Or remove this here.
On 2014/11/03 20:30:10, Nico wrote: > https://codereview.chromium.org/692313002/diff/20001/build/config/compiler/BU... > File build/config/compiler/BUILD.gn (right): > > https://codereview.chromium.org/692313002/diff/20001/build/config/compiler/BU... > build/config/compiler/BUILD.gn:754: "-Wno-type-limits", > If you want to keep this, I'd add it to the gyp build too. Or remove this here. I think I'll add it to the GYP build, as I'd like to record the knowledge somewhere for posterity.
https://codereview.chromium.org/692313002/diff/20001/build/config/compiler/BU... File build/config/compiler/BUILD.gn (right): https://codereview.chromium.org/692313002/diff/20001/build/config/compiler/BU... build/config/compiler/BUILD.gn:754: "-Wno-type-limits", On 2014/11/03 20:30:10, Nico wrote: > If you want to keep this, I'd add it to the gyp build too. Or remove this here. Done.
https://codereview.chromium.org/692313002/diff/40001/build/common.gypi File build/common.gypi (right): https://codereview.chromium.org/692313002/diff/40001/build/common.gypi#newcod... build/common.gypi:3555: '-Wno-type-limits', You only want to add this for gcc builds. clang builds are warning-free.
removed any reference to type-limits. Knowledge recorded in https://code.google.com/p/chromium/issues/detail?id=429804 for posterity
lgtm
On 2014/11/03 20:56:44, Nico wrote: > lgtm Brett, can I haz an OWNER LGTM?
On 2014/11/03 21:30:33, Chris Masone wrote: > On 2014/11/03 20:56:44, Nico wrote: > > lgtm > > Brett, can I haz an OWNER LGTM? Ping?
On 2014/11/04 21:47:31, Chris Masone wrote: > On 2014/11/03 21:30:33, Chris Masone wrote: > > On 2014/11/03 20:56:44, Nico wrote: > > > lgtm > > > > Brett, can I haz an OWNER LGTM? > > Ping? Since this matches gyp, I think it's fine to TBR=brettw this.
The CQ bit was checked by cmasone@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/692313002/60001
lgtm
Message was sent while issue was closed.
Committed patchset #4 (id:60001)
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/c9aa95f7873dc969f35cded9b4f2e2692af91b18 Cr-Commit-Position: refs/heads/master@{#302693} |
