https://gcc.gnu.org/g:90a4851b08270678352f4f53f86d94af78647499
commit r15-4304-g90a4851b08270678352f4f53f86d94af78647499
Author: Sam James <s...@gentoo.org>
Date:   Sun Oct 13 23:22:02 2024 +0100

    libstdc++: testsuite: adjust name_fortify test for pre-defined 
_FORTIFY_SOURCE
    
    Otherwise we get failures with toolchains that have _FORTIFY_SOURCE
    defined already to a different value like 3.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/17_intro/names_fortify.cc: Undefine _FORTIFY_SOURCE.

Diff:
---
 libstdc++-v3/testsuite/17_intro/names_fortify.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/libstdc++-v3/testsuite/17_intro/names_fortify.cc 
b/libstdc++-v3/testsuite/17_intro/names_fortify.cc
index c975412074be..f24af21f8a70 100644
--- a/libstdc++-v3/testsuite/17_intro/names_fortify.cc
+++ b/libstdc++-v3/testsuite/17_intro/names_fortify.cc
@@ -1,6 +1,7 @@
 // { dg-do compile { target *-*-linux* } }
 // { dg-add-options no_pch }
 
+#undef _FORTIFY_SOURCE
 #define _FORTIFY_SOURCE 2
 // Now we can define the macros to poison uses of non-reserved names:
 #include "names.cc"

Reply via email to