Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] mark structs2.exp tests as kfail on hppa
Date: Mon, 07 Jun 2004 19:12:00 -0000	[thread overview]
Message-ID: <20040607191200.GE30453@tausq.org> (raw)
In-Reply-To: <20040607185816.2A4274B104@berman.michael-chastain.com>

> "KFAIL" means known failure inside gdb.
> "XFAIL" means expected failure in something outside gdb (like gcc).
> 
> So these would be XFAIL's.  setup_xfail has a three-argument form
> so you can say "setup_xfail hppa-*-* gcc/15860".

thanks.

updated patch follows, if we want to put this in..

randolph


2004-06-07  Randolph Chung  <tausq@debian.org>

	* gdb.base/structs2.exp: Mark two tests as xfail 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 19:10:47 -0000
@@ -29,6 +29,12 @@ set testfile "structs2"
 set srcfile ${testfile}.c
 set binfile ${objdir}/${subdir}/${testfile}
 
+# Create and source the file that provides information about the compiler
+# used to compile the test case.
+if [get_compiler_info ${binfile}] {
+    return -1;
+}
+
 # build the first test case
 if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
     # built the second test case since we can't use prototypes
@@ -64,10 +70,16 @@ gdb_test "break param_reg" \
     "Breakpoint .* at .*" \
     "structs2 breakpoint set"
 
+if { [ test_compiler_info gcc-*-* ] } then {
+  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-*-* ] } then {
+  setup_xfail hppa*-* gcc/15860
+}
 gdb_test "continue" \
     ".*pr_char=-126.*pr_uchar=120.*pr_short=-32536.*pr_ushort=32000.*bkpt = 1.*" \
     "structs2 continue2"


  reply	other threads:[~2004-06-07 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 18:58 Michael Elizabeth Chastain
2004-06-07 19:12 ` Randolph Chung [this message]
2004-06-08 19:39   ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07 18:42 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=20040607191200.GE30453@tausq.org \
    --to=randolph@tausq.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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