From: Randolph Chung <randolph@tausq.org>
To: gdb-patches@sources.redhat.com
Subject: [patch/RFA] Remove xfail for hppa*-* for gdb.base/structs2.exp
Date: Wed, 09 Nov 2005 15:47:00 -0000 [thread overview]
Message-ID: <4371A5C1.30406@tausq.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]
gdb.base/structs2.exp had an xfail for hppa*-* due to a gcc bug. The gcc
bug has been fixed for some time (since October 2004), so we might want
to remove this xfail.
gcc bug is: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15860
ok to check in?
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
[-- Attachment #2: d --]
[-- Type: text/plain, Size: 1005 bytes --]
2005-11-09 Randolph Chung <tausq@debian.org>
* gdb.base/structs2.exp: Remove a xfail due to a gcc bug that
has since been fixed.
Index: gdb.base/structs2.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/structs2.exp,v
retrieving revision 1.3
diff -u -p -r1.3 structs2.exp
--- gdb.base/structs2.exp 11 Jun 2004 23:42:49 -0000 1.3
+++ gdb.base/structs2.exp 9 Nov 2005 07:26:27 -0000
@@ -70,16 +70,10 @@ gdb_test "break param_reg" \
"Breakpoint .* at .*" \
"structs2 breakpoint set"
-if [test_compiler_info gcc-*-*] {
- setup_xfail hppa*-* gcc/15860
-}
gdb_test "continue" \
".*pr_char=120.*pr_uchar=130.*pr_short=32000.*pr_ushort=33000.*bkpt = 1.*"
\
"structs2 continue1"
-if [test_compiler_info gcc-*-*] {
- setup_xfail hppa*-* gcc/15860
-}
gdb_test "continue" \
".*pr_char=-126.*pr_uchar=120.*pr_short=-32536.*pr_ushort=32000.*bkpt = 1.*
" \
"structs2 continue2"
next reply other threads:[~2005-11-09 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 15:47 Randolph Chung [this message]
2005-11-09 17:56 ` Randolph Chung
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=4371A5C1.30406@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