This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[patch/rfc] mark structs2.exp tests as kfail on hppa
- From: Randolph Chung <randolph at tausq dot org>
- To: gdb-patches at sources dot redhat dot com
- Date: Mon, 7 Jun 2004 11:42:13 -0700
- Subject: [patch/rfc] mark structs2.exp tests as kfail on hppa
- Reply-to: Randolph Chung <randolph at tausq dot org>
This is related to
http://sources.redhat.com/ml/gdb/2004-03/msg00043.html
Dan helped me look at this a bit more. The details are in a gcc bug
report:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15860
Should i mark the test as kfailed? I don't know what's the "common
practice" for marking gcc bugs in gdb test cases...
of course, this is also not entirely accurate, since the problem seems
to be with gcc and not the architecture itself.
randolph
2004-06-07 Randolph Chung <tausq@debian.org>
* gdb.base/structs2.exp: Mark two tests as kfail because of a compiler
problem.
Index: gdb.base/structs2.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/structs2.exp,v
retrieving revision 1.2
diff -u -p -r1.2 structs2.exp
--- gdb.base/structs2.exp 6 Mar 2001 08:21:51 -0000 1.2
+++ gdb.base/structs2.exp 7 Jun 2004 18:34:02 -0000
@@ -64,10 +64,12 @@ gdb_test "break param_reg" \
"Breakpoint .* at .*" \
"structs2 breakpoint set"
+setup_kfail "hppa*-*" gcc/15860
gdb_test "continue" \
".*pr_char=120.*pr_uchar=130.*pr_short=32000.*pr_ushort=33000.*bkpt = 1.*" \
"structs2 continue1"
+setup_kfail "hppa*-*" gcc/15860
gdb_test "continue" \
".*pr_char=-126.*pr_uchar=120.*pr_short=-32536.*pr_ushort=32000.*bkpt = 1.*" \
"structs2 continue2"
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/