Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/alpha] Add handling of FP control insn in software-single step
Date: Tue, 17 May 2005 05:46:00 -0000	[thread overview]
Message-ID: <20050517034410.GA21351@nevyn.them.org> (raw)
In-Reply-To: <20050517025048.GL12565@adacore.com>

On Tue, May 17, 2005 at 12:50:48PM +1000, Joel Brobecker wrote:
> > On Tue, May 17, 2005 at 12:34:00PM +1000, Joel Brobecker wrote:
> > > Tested on alpha-tru64 5.1a with no regression. It fixes a problem with
> > > some code but I can't contribute it, as it has been given to us by a
> > > customer.
> > 
> > Can you write a test for this in gdb.arch, using an asm to provide the
> > fbeq instruction that was causing a problem?
> 
> Let me see what I can do. I tend to prefer tests written in C or Ada,
> as it can be used on all platforms rather than just on alpha. But
> perhaps the usage in this case is to prefer asm?

The feature you're implementing is specific to Alpha; think of it in
the nature of unit testing.

That's not to say a test for "single step over a floating point
compare-and-branch" would be a bad thing to have in the rest of the
testsuite.  But I'm sure you can imagine how hard it is to predict what
a compiler will generate.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-05-17  3:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  2:50 Joel Brobecker
2005-05-17  3:44 ` Daniel Jacobowitz
2005-05-17  4:49   ` Joel Brobecker
2005-05-17  5:46     ` Daniel Jacobowitz [this message]
2005-05-17  6:22       ` Joel Brobecker
2005-05-17  6:30         ` Mark Kettenis
2005-05-17  8:02 ` Richard Henderson
2005-05-17 10:21 ` Richard Henderson
2005-05-17 13:24   ` Joel Brobecker

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=20050517034410.GA21351@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.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