Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFA: Test ability to access i386 SSE registers
Date: Mon, 07 Jun 2004 15:40:00 -0000	[thread overview]
Message-ID: <vt2vfi39y2s.fsf@zenia.home> (raw)
In-Reply-To: <vt24qqmqhc8.fsf@zenia.home>


Jim Blandy <jimb@redhat.com> writes:

> Daniel Jacobowitz <drow@false.org> writes:
> 
> > On Wed, May 12, 2004 at 12:25:40AM -0500, Jim Blandy wrote:
> > > 
> > > It's late; there is surely some Kool-Aid around here I have forgotten
> > > to drink.
> > 
> > There better be!
> > 
> > > + if ![runto_main] then {
> > > +     gdb_suppress_tests
> > > + }
> > > + 
> > > + gdb_test "break [gdb_get_line_number "first breakpoint here"]" \
> > > +          "Breakpoint .* at .*i386-sse.c.*" \
> > > +          "set breakpoint in main"
> > > + gdb_continue_to_breakpoint "continue to first breakpoint in main"
> > 
> > So, all that trouble to make the SSE testcase not use movaps if it
> > isn't available... and you never check in the test script?
> 
> Oh yeah.  That was it.  [vacant stare]
> 
> > If you're going to be thorough in the test case, be more thorough.  See
> > gcc.dg/i386-cpuid.h in GCC.
> 
> Okay.  How about:
> 
> 2004-05-12  Jim Blandy  <jimb@redhat.com>
> 
> 	* gdb.arch/i386-sse.exp, gdb.arch/i386-sse.c: New tests.
> 	* gdb.arch/i386-cpuid.h: New helper file.

I've committed this test as revised.


      reply	other threads:[~2004-06-07 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12  5:26 Jim Blandy
2004-05-12  6:09 ` Daniel Jacobowitz
2004-05-12  6:40   ` Jim Blandy
2004-06-07 15:40     ` Jim Blandy [this message]

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=vt2vfi39y2s.fsf@zenia.home \
    --to=jimb@redhat.com \
    --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