public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc(refs/users/aoliva/heads/testme)] testsuite: arm: fix arm_movt cut&pasto
@ 2023-11-19  8:11 Alexandre Oliva
  0 siblings, 0 replies; 3+ messages in thread
From: Alexandre Oliva @ 2023-11-19  8:11 UTC (permalink / raw)
  To: gcc-cvs

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

commit ff0f1d111893309521e776866497bf8a4de67dfe
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Nov 19 02:41:48 2023 -0300

    testsuite: arm: fix arm_movt cut&pasto
    
    I got spurious fails of tests that required arm_thumb1_movt_ok on a
    target cpu that did not support movt.  Looking into it, I found the
    arm_movt property to have been cut&pasted into various procs that
    checked for different properties.  They shouldn't share the same test
    results cache entry, so I'm changing their prop names.
    
    
    for  gcc/testsuite/ChangeLog
    
            * lib/target-supports.exp
            (check_effective_target_arm_thumb1_cbz_ok): Fix prop name
            cut&pasto.
            (check_effective_target_arm_arch_v6t2_hw_ok): Likewise.

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 240a3815d38..e3519207d0e 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -5610,7 +5610,7 @@ proc check_effective_target_arm_thumb1_movt_ok {} {
 
 proc check_effective_target_arm_thumb1_cbz_ok {} {
     if [check_effective_target_arm_thumb1_ok] {
-	return [check_no_compiler_messages arm_movt object {
+	return [check_no_compiler_messages arm_cbz object {
 	    int
 	    foo (void)
 	    {
@@ -5627,7 +5627,7 @@ proc check_effective_target_arm_thumb1_cbz_ok {} {
 
 proc check_effective_target_arm_arch_v6t2_hw_ok {} {
     if [check_effective_target_arm_thumb1_ok] {
-	return [check_no_compiler_messages arm_movt object {
+	return [check_no_compiler_messages arm_v6t2_hw object {
 	    int
 	    main (void)
 	    {

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [gcc(refs/users/aoliva/heads/testme)] testsuite: arm: fix arm_movt cut&pasto
@ 2023-11-19  7:02 Alexandre Oliva
  0 siblings, 0 replies; 3+ messages in thread
From: Alexandre Oliva @ 2023-11-19  7:02 UTC (permalink / raw)
  To: gcc-cvs

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

commit fd8c60d0f2a2713bc3108918a9e025abee83e458
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Nov 19 02:41:48 2023 -0300

    testsuite: arm: fix arm_movt cut&pasto
    
    I got spurious fails of tests that required arm_thumb1_movt_ok on a
    target cpu that did not support movt.  Looking into it, I found the
    arm_movt property to have been cut&pasted into various procs that
    checked for different properties.  They shouldn't share the same test
    results cache entry, so I'm changing their prop names.
    
    
    for  gcc/testsuite/ChangeLog
    
            * lib/target-supports.exp
            (check_effective_target_arm_thumb1_cbz_ok): Fix prop name
            cut&pasto.
            (check_effective_target_arm_arch_v6t2_hw_ok): Likewise.

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 240a3815d38..e3519207d0e 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -5610,7 +5610,7 @@ proc check_effective_target_arm_thumb1_movt_ok {} {
 
 proc check_effective_target_arm_thumb1_cbz_ok {} {
     if [check_effective_target_arm_thumb1_ok] {
-	return [check_no_compiler_messages arm_movt object {
+	return [check_no_compiler_messages arm_cbz object {
 	    int
 	    foo (void)
 	    {
@@ -5627,7 +5627,7 @@ proc check_effective_target_arm_thumb1_cbz_ok {} {
 
 proc check_effective_target_arm_arch_v6t2_hw_ok {} {
     if [check_effective_target_arm_thumb1_ok] {
-	return [check_no_compiler_messages arm_movt object {
+	return [check_no_compiler_messages arm_v6t2_hw object {
 	    int
 	    main (void)
 	    {

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [gcc(refs/users/aoliva/heads/testme)] testsuite: arm: fix arm_movt cut&pasto
@ 2023-11-19  6:31 Alexandre Oliva
  0 siblings, 0 replies; 3+ messages in thread
From: Alexandre Oliva @ 2023-11-19  6:31 UTC (permalink / raw)
  To: gcc-cvs

https://gcc.gnu.org/g:47c3446bd87091babe7a03e61f5857a846ea61b9

commit 47c3446bd87091babe7a03e61f5857a846ea61b9
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Nov 19 02:41:48 2023 -0300

    testsuite: arm: fix arm_movt cut&pasto
    
    I got spurious fails of tests that required arm_thumb1_movt_ok on a
    target cpu that did not support movt.  Looking into it, I found the
    arm_movt property to have been cut&pasted into various procs that
    checked for different properties.  They shouldn't share the same test
    results cache entry, so I'm changing their prop names.
    
    
    for  gcc/testsuite/ChangeLog
    
            * lib/target-supports.exp
            (check_effective_target_arm_thumb1_cbz_ok): Fix prop name
            cut&pasto.
            (check_effective_target_arm_arch_v6t2_hw_ok): Likewise.

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 240a3815d38..e3519207d0e 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -5610,7 +5610,7 @@ proc check_effective_target_arm_thumb1_movt_ok {} {
 
 proc check_effective_target_arm_thumb1_cbz_ok {} {
     if [check_effective_target_arm_thumb1_ok] {
-	return [check_no_compiler_messages arm_movt object {
+	return [check_no_compiler_messages arm_cbz object {
 	    int
 	    foo (void)
 	    {
@@ -5627,7 +5627,7 @@ proc check_effective_target_arm_thumb1_cbz_ok {} {
 
 proc check_effective_target_arm_arch_v6t2_hw_ok {} {
     if [check_effective_target_arm_thumb1_ok] {
-	return [check_no_compiler_messages arm_movt object {
+	return [check_no_compiler_messages arm_v6t2_hw object {
 	    int
 	    main (void)
 	    {

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-11-19  8:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-19  8:11 [gcc(refs/users/aoliva/heads/testme)] testsuite: arm: fix arm_movt cut&pasto Alexandre Oliva
  -- strict thread matches above, loose matches on Subject: below --
2023-11-19  7:02 Alexandre Oliva
2023-11-19  6:31 Alexandre Oliva

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).