commit 067bdc9546557a1a107f2617d7d15b864ff493f1
author Elliott Hughes <enh@google.com> Mon Jul 23 16:53:12 2018 -0700
committer Elliott Hughes <enh@google.com> Mon Jul 23 17:22:58 2018 -0700
tree 48a51876da8e0a43c2c46393d03a599f016dceae
parent 94ab04c17a0e9f412b7de079f2ef35f39c7f06fc

Retire GCC FORTIFY.

NDK r18 (which removes GCC) is about to ship. We don't need this any more.

The immediate motivation for removing this right now is that the test
fails whenever we add Clang-only flags to the build system.

While we're here, clean up <stdatomic.h> too.

Bug: https://issuetracker.google.com/74404306
Test: ran tests
Change-Id: Iaad5d634d1ba76f0b6f19ad32cc27b2533771a4a

libc/include/string.h

diff --git a/libc/include/string.h b/libc/include/string.h
index 54d5e1c..25f6673 100644
--- a/libc/include/string.h
+++ b/libc/include/string.h
@@ -144,7 +144,7 @@
 #endif
 
 /* Const-correct overloads. Placed after FORTIFY so we call those functions, if possible. */
-#if defined(__cplusplus) && defined(__clang__)
+#if defined(__cplusplus)
 /*
  * Use two enable_ifs so these overloads don't conflict with + are preferred over libcxx's. This can
  * be reduced to 1 after libcxx recognizes that we have const-correct overloads.