[gcc(refs/users/aoliva/heads/testme)] force run test of pr95401 - local workaround

[gcc(refs/users/aoliva/heads/testme)] force run test of pr95401 - local workaround

[Alexandre Oliva]

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

commit b756057c41e284722db2c0aaf64dcb0baf6f16bc
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Tue Mar 9 18:43:10 2021 -0300

    force run test of pr95401 - local workaround
    
    When vect.exp finds our configuration disables altivec by default, it
    disables the execution of vectorization tests, assuming the test
    hardware doesn't support it.
    
    Tests become just compile tests, which gives us some coverage, but
    compile tests won't work correctly when additional sources are named,
    e.g. pr95401.cc, because GCC refuses to compile multiple files into
    the same asm output.
    
    This local workaround turns pr95401 into an execution test
    regardless.  Perhaps we should retain them all?
    
    
    for  gcc/testsuite/ChangeLog
    
            * g++.dg/vect/pr95401.cc: Mark as run test unconditionally.

Diff:
---
 gcc/testsuite/lib/target-supports.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index 52d3d036d3c..23d532fb2b9 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -9656,7 +9656,7 @@ proc check_vect_support_and_set_flags { } {
                 # Specify a cpu that supports VMX for compile-only tests.
                 lappend DEFAULT_VECTCFLAGS "-mcpu=970"
             }
-            set dg-do-what-default compile
+            set dg-do-what-default link
         }
     } elseif { [istarget i?86-*-*] || [istarget x86_64-*-*] } {
         lappend DEFAULT_VECTCFLAGS "-msse2"

[gcc(refs/users/aoliva/heads/testme)] force run test of pr95401 - local workaround

[Alexandre Oliva]

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

commit e28fc7d0eb15b303be080888ab7de9f6b89c27a4
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Mar 8 23:22:53 2021 -0300

    force run test of pr95401 - local workaround
    
    When vect.exp finds our configuration disables altivec by default, it
    disables the execution of vectorization tests, assuming the test
    hardware doesn't support it.
    
    Tests become just compile tests, which gives us some coverage, but
    compile tests won't work correctly when additional sources are named,
    e.g. pr95401.cc, because GCC refuses to compile multiple files into
    the same asm output.
    
    This local workaround turns pr95401 into an execution test
    regardless.  Perhaps we should retain them all?
    
    
    for  gcc/testsuite/ChangeLog
    
            * g++.dg/vect/pr95401.cc: Mark as run test unconditionally.

Diff:
---
 gcc/testsuite/lib/target-supports.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index 570d5d3de00..d01b90737f7 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -9641,7 +9641,7 @@ proc check_vect_support_and_set_flags { } {
                 # Specify a cpu that supports VMX for compile-only tests.
                 lappend DEFAULT_VECTCFLAGS "-mcpu=970"
             }
-            set dg-do-what-default compile
+            set dg-do-what-default link
         }
     } elseif { [istarget i?86-*-*] || [istarget x86_64-*-*] } {
         lappend DEFAULT_VECTCFLAGS "-msse2"

[gcc(refs/users/aoliva/heads/testme)] force run test of pr95401 - local workaround

[Alexandre Oliva]

https://gcc.gnu.org/g:95576a95f4aa3cc6517167805a5bca17f57579ad

commit 95576a95f4aa3cc6517167805a5bca17f57579ad
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Mar 8 23:22:53 2021 -0300

    force run test of pr95401 - local workaround
    
    When vect.exp finds our configuration disables altivec by default, it
    disables the execution of vectorization tests, assuming the test
    hardware doesn't support it.
    
    Tests become just compile tests, which gives us some coverage, but
    compile tests won't work correctly when additional sources are named,
    e.g. pr95401.cc, because GCC refuses to compile multiple files into
    the same asm output.
    
    This local workaround turns pr95401 into an execution test
    regardless.  Perhaps we should retain them all?
    
    
    for  gcc/testsuite/ChangeLog
    
            * g++.dg/vect/pr95401.cc: Mark as run test unconditionally.

Diff:
---
 gcc/testsuite/lib/target-supports.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index 570d5d3de00..d01b90737f7 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -9641,7 +9641,7 @@ proc check_vect_support_and_set_flags { } {
                 # Specify a cpu that supports VMX for compile-only tests.
                 lappend DEFAULT_VECTCFLAGS "-mcpu=970"
             }
-            set dg-do-what-default compile
+            set dg-do-what-default link
         }
     } elseif { [istarget i?86-*-*] || [istarget x86_64-*-*] } {
         lappend DEFAULT_VECTCFLAGS "-msse2"

[gcc(refs/users/aoliva/heads/testme)] force run test of pr95401 - local workaround

[Alexandre Oliva]

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

commit a3ee355f650630aadfb849d266593f8f145c3a9a
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Mar 8 23:22:53 2021 -0300

    force run test of pr95401 - local workaround
    
    When vect.exp finds our configuration disables altivec by default, it
    disables the execution of vectorization tests, assuming the test
    hardware doesn't support it.
    
    Tests become just compile tests, which gives us some coverage, but
    compile tests won't work correctly when additional sources are named,
    e.g. pr95401.cc, because GCC refuses to compile multiple files into
    the same asm output.
    
    This local workaround turns pr95401 into an execution test
    regardless.  Perhaps we should retain them all?
    
    
    for  gcc/testsuite/ChangeLog
    
            * g++.dg/vect/pr95401.cc: Mark as run test unconditionally.

Diff:
---
 gcc/testsuite/lib/target-supports.exp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index 570d5d3de00..6aec927ff91 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -9634,14 +9634,14 @@ proc check_vect_support_and_set_flags { } {
             lappend DEFAULT_VECTCFLAGS "-mvsx" "-mno-allow-movmisalign"
         }
 
-        if [check_vmx_hw_available] {
+        if { [check_vmx_hw_available] } {
             set dg-do-what-default run
         } else {
             if [is-effective-target ilp32] {
                 # Specify a cpu that supports VMX for compile-only tests.
                 lappend DEFAULT_VECTCFLAGS "-mcpu=970"
             }
-            set dg-do-what-default compile
+            set dg-do-what-default link
         }
     } elseif { [istarget i?86-*-*] || [istarget x86_64-*-*] } {
         lappend DEFAULT_VECTCFLAGS "-msse2"