diff options
| author | Alexandre Oliva <oliva@adacore.com> | 2023-11-19 02:41:48 -0300 |
|---|---|---|
| committer | Alexandre Oliva <oliva@gnu.org> | 2023-11-20 05:16:36 -0300 |
| commit | 4b51c7c9131280edd1c97053e2b07a33ec0b5501 (patch) | |
| tree | 1bb7fb3de4fe7912e3ce4fc8ef94c432ef92b705 | |
| parent | 0e0e3420dfe1d302145b4eb3bbf311a4f39eeced (diff) | |
| download | gcc-4b51c7c9131280edd1c97053e2b07a33ec0b5501.zip gcc-4b51c7c9131280edd1c97053e2b07a33ec0b5501.tar.gz gcc-4b51c7c9131280edd1c97053e2b07a33ec0b5501.tar.bz2 | |
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.
| -rw-r--r-- | gcc/testsuite/lib/target-supports.exp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index 7412ac9..4b647d6 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) { |