Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(200)

Unified Diff: build/config/compiler/BUILD.gn

Issue 1127993006: Define _FORTIFY_SOURCE=2 under the same conditions in gn as gyp. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@gn-tsan
Patch Set: Created 5 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: build/config/compiler/BUILD.gn
diff --git a/build/config/compiler/BUILD.gn b/build/config/compiler/BUILD.gn
index 2ef116ce87df01b155b99fe7cb240cd45b31bcd3..256b3e3efebfbe343aeef9d0b564e0a6b9ed69b0 100644
--- a/build/config/compiler/BUILD.gn
+++ b/build/config/compiler/BUILD.gn
@@ -662,7 +662,7 @@ config("chromium_code") {
"__STDC_FORMAT_MACROS",
]
- if (using_sanitizer) {
+ if (!using_sanitizer && (!is_linux || !is_clang || is_official_build)) {
Dirk Pranke 2015/05/19 19:53:30 I can see this matches the logic in GYP, but tryin
Sam McNally 2015/05/20 01:40:29 My understanding from the comments is that we want
Nico 2015/05/21 19:19:55 Yes, this is correct.
# _FORTIFY_SOURCE isn't really supported by Clang now, see
# http://llvm.org/bugs/show_bug.cgi?id=16821.
# It seems to work fine with Ubuntu 12 headers though, so use it in
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698