Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com, jimb@redhat.com
Subject: Re: [rfc/testsuite] i386-sse.exp: better output if no SSE support
Date: Thu, 17 Jun 2004 19:07:00 -0000	[thread overview]
Message-ID: <20040617190659.GA28934@nevyn.them.org> (raw)
In-Reply-To: <20040617185658.223484B104@berman.michael-chastain.com>

On Thu, Jun 17, 2004 at 02:56:58PM -0400, Michael Chastain wrote:
> This patch fixes i386-sse.exp for compilers that don't support SSE,
> specifically gcc 2.95.3.  Before this patch, the results are:
> 
>    3 ERROR
>    2 WARNING
>   33 FAIL
>    1 UNRESOLVED
> 
> After this patch, the results are a single UNSUPPORTED.
> My view is that people should be reading all their non-PASS results,
> including the UNRESOLVED, UNSUPPORTED, and UNTESTED results.
> We might want to discuss this.

As far as I'm concerned this is absolutely a good change.  I don't
always carefully read the UNSUPPORTED / UNTESTED results, but I do at
least look at them.  And anything that makes gdb_suppress_entire_file
go away is good in my book.

> 	Fix PR testsuite/1679.
> 	* gdb.arch/i386-sse.exp: Do not call gdb_suppress_entire file.
> 	Issue an UNSUPPORTED result instead.

"entire_file".


-- 
Daniel Jacobowitz


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 18:57 Michael Elizabeth Chastain
2004-06-17 19:07 ` Daniel Jacobowitz [this message]
2004-06-17 20:40 ` Jim Blandy
2004-06-19 18:59 Michael Elizabeth Chastain

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=20040617190659.GA28934@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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