Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
		gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [rfc][1/2] add suport for 64-bit fpscr in powerpc linux native
Date: Tue, 18 Nov 2008 05:46:00 -0000	[thread overview]
Message-ID: <20081117221839.GA2536@caradoc.them.org> (raw)
In-Reply-To: <1226959224.28256.38.camel@localhost.localdomain>

On Mon, Nov 17, 2008 at 08:00:23PM -0200, Thiago Jung Bauermann wrote:
> If linking to the expat library wasn't optional when building GDB, one
> option would be to provide just the power-fpu-isa205.xml file containing
> the feature description, and then generate the target description XML on
> the fly including the appropriate features, and have GDB parse that.

There's another way you could do it... if the individual features
could be compiled to C instead of just entire descriptions you could
call their generated functions.  It's not set up to work that way
at the moment.  I don't know if it would be an easy change or a messy
one.
> > > +gdb_test "print/t \$fpscr" " = 10100000000000000000000000000000000" "FPSCR for round to nearest, ties toward zero rounding mode"
> > 
> > Just a casual remark, not a request for change, but I'm surprised
> > that you might find /t more useful in this case than /x ;-).
> 
> I agree in general /x is more helpful, but in this case binary was
> easier because the FPSCR is just a bunch of flags, so I could directly
> see which were set and which weren't.
> 
> Ok, I admit I still don't do my taxes in hex. :-)

You do them in binary?

Anyway, you might want to consider adding a flags type, like x86
%eflags, for $fpscr.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-11-17 22:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15  0:02 Thiago Jung Bauermann
2008-09-24 20:32 ` Thiago Jung Bauermann
2008-11-13 20:06   ` Thiago Jung Bauermann
2008-11-14 11:32 ` Joel Brobecker
2008-11-14 11:36   ` Joel Brobecker
2008-11-18  5:45     ` Thiago Jung Bauermann
2008-11-18  5:46       ` Daniel Jacobowitz [this message]
2008-11-19 13:30       ` Thiago Jung Bauermann

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=20081117221839.GA2536@caradoc.them.org \
    --to=drow@false.org \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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