Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	        Luis Machado <luisgpm@linux.vnet.ibm.com>,
	gdb-patches@sourceware.org
Subject: Re: Printing decimal128 types out of registers
Date: Wed, 23 Jan 2008 16:56:00 -0000	[thread overview]
Message-ID: <1201107379.11950.70.camel@localhost.localdomain> (raw)
In-Reply-To: <20080123152007.GA8286@caradoc.them.org>

On Wed, 2008-01-23 at 10:20 -0500, Daniel Jacobowitz wrote:
> Here's one (of many) possible ways you could do it.  Define an
> appropriate property in an XML file for Power6, and add that to the
> list of built-in descriptions just like the existing ones.  In
> ppc-linux-nat.c and in gdbserver, check the auxv vector for the
> dfp capability.  If it's present, return the Power6 description.
> Other non-Linux targets can handle this in the appropriate way
> for each target.
> 
> For the gdbserver part you'd probably want to wait until Ulrich's
> biarch patches go in; that may simplify it.

I'll try this. Thanks for the suggestion.

> If this is too complicated, I wouldn't argue against a patch that just
> added them if the floating point regsiters are present.  Seems like it
> won't be useful on a lot of processors though.

Agreed.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center


  reply	other threads:[~2008-01-23 16:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 19:33 [PATCH] PPC - Printing Decimal 128 " Luis Machado
2007-11-26 21:40 ` Luis Machado
2007-12-26 12:42   ` [PING] " Luis Machado
2008-01-17 19:03 ` Printing decimal128 " Luis Machado
2008-01-17 19:36   ` Thiago Jung Bauermann
2008-01-18 15:43     ` Luis Machado
2008-01-18 16:12       ` Mark Kettenis
2008-01-18 16:38         ` Luis Machado
2008-01-18 17:20           ` Mark Kettenis
2008-01-18 18:52             ` Luis Machado
2008-01-18 19:54               ` Mark Kettenis
2008-01-19  0:04       ` Daniel Jacobowitz
2008-01-21 14:55         ` Thiago Jung Bauermann
2008-01-21 17:31           ` Mark Kettenis
2008-01-23 15:39             ` Thiago Jung Bauermann
2008-01-21 17:54     ` Daniel Jacobowitz
2008-01-23 15:11       ` Thiago Jung Bauermann
2008-01-23 15:20         ` Daniel Jacobowitz
2008-01-23 16:56           ` Thiago Jung Bauermann [this message]
2008-01-30 15:46           ` Thiago Jung Bauermann
2008-01-30 16:45             ` Thiago Jung Bauermann
2008-01-30 18:27             ` Mark Kettenis
2008-01-30 18:38               ` Thiago Jung Bauermann
2008-01-30 20:28                 ` Mark Kettenis
2008-01-30 21:26                   ` Thiago Jung Bauermann
2008-01-30 21:39                     ` Ulrich Weigand
2008-01-31 14:47                       ` Thiago Jung Bauermann
2008-01-31 15:06                         ` Ulrich Weigand
2008-01-30 21:42                     ` Mark Kettenis
2008-01-30 23:03                     ` Eli Zaretskii
2008-01-31 15:44                       ` 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=1201107379.11950.70.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.com \
    --cc=mark.kettenis@xs4all.nl \
    /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