diff options
author | Tom de Vries <tdevries@jostaberry-8.arch.suse.de> | 2022-11-17 09:11:47 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2022-11-17 09:11:47 +0100 |
commit | 7a4ce4a1bcff9710b7dede9797e6d5eb2364c06e (patch) | |
tree | 5c6708a3fc4ffe5dc83ee5e124e649437d3cad03 | |
parent | d5b9201744fa1dcfcde2e06140efe28819aaef25 (diff) | |
download | gdb-7a4ce4a1bcff9710b7dede9797e6d5eb2364c06e.zip gdb-7a4ce4a1bcff9710b7dede9797e6d5eb2364c06e.tar.gz gdb-7a4ce4a1bcff9710b7dede9797e6d5eb2364c06e.tar.bz2 |
[gdb/testsuite] Fix DUPLICATE in gdb.arch/ppc-fp.exp
I noticed:
...
DUPLICATE: gdb.arch/ppc-fp.exp: next
...
Fix this by adding unique test names.
Tested on powerpc64le-linux.
-rw-r--r-- | gdb/testsuite/gdb.arch/ppc-fp.exp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/testsuite/gdb.arch/ppc-fp.exp b/gdb/testsuite/gdb.arch/ppc-fp.exp index bf1a1c5..bd22d7c 100644 --- a/gdb/testsuite/gdb.arch/ppc-fp.exp +++ b/gdb/testsuite/gdb.arch/ppc-fp.exp @@ -61,7 +61,7 @@ gdb_test_multiple "print \$fpscr" "FPSCR exists" { } # Step over invalid operation. -gdb_test "next" "" "" +gdb_test "next" "" "next over invalid operation" # Verify that the following bits are set (See Power ISA for details): # @@ -75,7 +75,7 @@ gdb_test "print/t \$fpscr" " = 10100000001000010001000000000000" "FPSCR for inva gdb_continue_to_breakpoint "go to division by zero" # Step over division by zero. -gdb_test "next" "" "" +gdb_test "next" "" "next over division by zero" # Verify that the following bits are set (See Power ISA for details): # |