[compiler-rt] ca50897 - [compiler-rt] Fix FORTIFY_SOURCE -> _FORTIFY_SOURCE reference (NFC)

[Sam James via llvm-commits]

Author: Sam James
Date: 2023-02-04T18:05:26Z
New Revision: ca50897a763c7dd0ec7c9b3ec003eeca802c5525

URL: https://github.com/llvm/llvm-project/commit/ca50897a763c7dd0ec7c9b3ec003eeca802c5525
DIFF: https://github.com/llvm/llvm-project/commit/ca50897a763c7dd0ec7c9b3ec003eeca802c5525.diff

LOG: [compiler-rt] Fix FORTIFY_SOURCE -> _FORTIFY_SOURCE reference (NFC)

As pointed out by maskray.

Fixes: 8ab762557fb057af1a3015211ee116a975027e78

Added: 
    

Modified: 
    compiler-rt/test/lit.common.cfg.py

Removed: 
    


################################################################################
diff  --git a/compiler-rt/test/lit.common.cfg.py b/compiler-rt/test/lit.common.cfg.py
index a4d2495beddb..5a6f04afffed 100644
--- a/compiler-rt/test/lit.common.cfg.py
+++ b/compiler-rt/test/lit.common.cfg.py
@@ -738,5 +738,5 @@ def is_windows_lto_supported():
 # possibly be present in system and user configuration files, so disable
 # default configs for the test runs. In particular, anything hardening
 # related is likely to cause issues with sanitizer tests, because it may
-# preempt something we're looking to trap (e.g. FORTIFY_SOURCE vs our ASAN).
+# preempt something we're looking to trap (e.g. _FORTIFY_SOURCE vs our ASAN).
 config.environment["CLANG_NO_DEFAULT_CONFIG"] = "1"