From c1e2a2c74cfe4086e5b72741a96780fd09bd4d7c Mon Sep 17 00:00:00 2001 From: Allan Sandfeld Jensen Date: Wed, 29 Nov 2017 15:42:57 +0100 Subject: Reduce warning flood when compiling with clang "cause the night is crap and full of warnings" Change-Id: Ic391ac12428c23ccfde8bc4aa5eaa0fa64235ff3 Reviewed-by: Alexandru Croitor --- chromium/build/config/compiler/BUILD.gn | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'chromium/build') diff --git a/chromium/build/config/compiler/BUILD.gn b/chromium/build/config/compiler/BUILD.gn index 2650d72ce99..fe2e1df4df8 100644 --- a/chromium/build/config/compiler/BUILD.gn +++ b/chromium/build/config/compiler/BUILD.gn @@ -311,9 +311,13 @@ config("compiler") { "-Wno-unknown-attributes", "-Wno-unknown-warning-option" ] + cflags_cc += [ + "-Wno-parentheses-equality", + "-Wno-tautological-compare" + ] } - if (is_clang && is_debug) { + if (is_clang && (is_debug || use_qt)) { # Allow comparing the address of references and 'this' against 0 # in debug builds. Technically, these can never be null in # well-defined C/C++ and Clang can optimize such checks away in -- cgit v1.2.1