Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com, jimb@redhat.com
Subject: Re: RFA: properly skip interrupts.exp
Date: Fri, 01 Mar 2002 21:45:00 -0000	[thread overview]
Message-ID: <200203020545.g225jaq20874@duracef.shout.net> (raw)

I have doubts about this.  It seems plausible to me that "nointerrupts"
is a property of the host, not the target.  gdb.base/interrupt.exp
seems very host oriented to me.

But dejagnu 1.4.2 has just two boards that set this:

  baseboards.exp/dos.exp
  baseboards.exp/m68hc11-sim.exp

I don't really know whether host or target is correct, and I don't
know what will happen with a switch.  Sigh.

I'm inclined to rip out "nointerrupts", rip out the years of
"setup_xfail" crud, and let the FAILs fall where they may.
But not with the 5.2 branch and 5.2 release imminent.

Michael C


             reply	other threads:[~2002-03-02  5:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 21:45 Michael Elizabeth Chastain [this message]
2002-03-04 18:27 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2002-03-01 15:10 Jim Blandy
2002-06-20 11:25 ` Jim Blandy
2002-07-12 16:22   ` Andrew Cagney
2002-07-18 17:02     ` Jim Blandy

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=200203020545.g225jaq20874@duracef.shout.net \
    --to=mec@shout.net \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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