From: Randolph Chung <randolph@tausq.org>
To: gdb-patches@sources.redhat.com
Subject: [patch/rfc] mark structs2.exp tests as kfail on hppa
Date: Mon, 07 Jun 2004 18:42:00 -0000 [thread overview]
Message-ID: <20040607184213.GD30453@tausq.org> (raw)
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/
next reply other threads:[~2004-06-07 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 18:42 Randolph Chung [this message]
2004-06-07 18:58 Michael Elizabeth Chastain
2004-06-07 19:12 ` Randolph Chung
2004-06-08 19:39 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040607184213.GD30453@tausq.org \
--to=randolph@tausq.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox