https://gcc.gnu.org/g:b21d64742e9cffafeb7c4c2b131bf622aaf38dbe

commit r15-3168-gb21d64742e9cffafeb7c4c2b131bf622aaf38dbe
Author: Dimitar Dimitrov <dimi...@dinux.eu>
Date:   Tue Aug 6 21:47:24 2024 +0300

    testsuite: Run array54.C only for sync_int_long targets
    
    The test case uses "atomic<int>", which fails to link on
    pru-unknown-elf target due to missing __atomic_load_4 symbol.
    
    Fix by filtering for sync_int_long effective target.  Ensured that the
    test still passes for x86_64-pc-linux-gnu.
    
    gcc/testsuite/ChangeLog:
    
            * g++.dg/init/array54.C: Require sync_int_long effective target.
    
    Signed-off-by: Dimitar Dimitrov <dimi...@dinux.eu>

Diff:
---
 gcc/testsuite/g++.dg/init/array54.C | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/g++.dg/init/array54.C 
b/gcc/testsuite/g++.dg/init/array54.C
index 5241e451d6d9..d664b5769849 100644
--- a/gcc/testsuite/g++.dg/init/array54.C
+++ b/gcc/testsuite/g++.dg/init/array54.C
@@ -1,6 +1,7 @@
 // PR c++/90947
 // { dg-do run { target c++11 } }
 // { dg-require-effective-target thread_fence }
+// { dg-require-effective-target sync_int_long }
 
 #include <atomic>

Reply via email to