[gcc r14-5610] testsuite: arm: fix arm_movt cut&pasto

[gcc r14-5610] testsuite: arm: fix arm_movt cut&pasto

[Alexandre Oliva]

https://gcc.gnu.org/g:4b51c7c9131280edd1c97053e2b07a33ec0b5501

commit r14-5610-g4b51c7c9131280edd1c97053e2b07a33ec0b5501
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 other procs that
    checked for different properties.  They shouldn't share the same test
    results cache entry, so I'm changing their prop names.  Or rather its
    prop name, because the other occurrence was already fixed recently.
    
    
    for  gcc/testsuite/ChangeLog
    
            * lib/target-supports.exp
            (check_effective_target_arm_thumb1_cbz_ok): Fix prop name
            cut&pasto.

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 7412ac95623..4b647d6a88e 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -5592,7 +5592,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)
 	    {