This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[commit] Another obvious altivec-regs.exp fix
- From: Paul Gilliam <pgilliam at us dot ibm dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Tue, 13 Sep 2005 16:17:23 -0700
- Subject: [commit] Another obvious altivec-regs.exp fix
- Reply-to: pgilliam at us dot ibm dot com
When the test checks the output from 'info reg vrsave' and 'info reg vscr', it expects only hex. This fix
makes it also expect the hex value to be followed by the decimal value.
2005-09-13 Paul Gilliam <pgilliam@us.ibm.com>
* gdb.arch/altivec-regs.exp: Adjust "info reg vrsave" and "info reg
vscr" tests to match output.
Index: gdb/testsuite/gdb.arch/altivec-regs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.arch/altivec-regs.exp,v
retrieving revision 1.4
diff -a -u -r1.4 altivec-regs.exp
--- gdb/testsuite/gdb.arch/altivec-regs.exp 3 May 2005 00:41:49 -0000 1.4
+++ gdb/testsuite/gdb.arch/altivec-regs.exp 13 Sep 2005 20:16:34 -0000
@@ -113,8 +113,8 @@
gdb_test "info reg vr$i" "vr$i.*$vector_register" "info reg vr$i"
}
-gdb_test "info reg vrsave" "vrsave.*0x1" "info reg vrsave"
-gdb_test "info reg vscr" "vscr.*0x1" "info reg vscr"
+gdb_test "info reg vrsave" "vrsave.*0x1 +1" "info reg vrsave"
+gdb_test "info reg vscr" "vscr.*0x1 +1" "info reg vscr"
# Now redo the same tests, but using the print command.
# Note: in LE case, the char array is printed WITHOUT the last character.