Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: luisgpm@linux.vnet.ibm.com
Cc: bauerman@br.ibm.com, gdb-patches@sourceware.org
Subject: Re: Printing decimal128 types out of registers
Date: Fri, 18 Jan 2008 17:20:00 -0000	[thread overview]
Message-ID: <200801181702.m0IH2W0E028191@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <1200674282.10815.10.camel@gargoyle> (message from Luis Machado 	on Fri, 18 Jan 2008 14:38:02 -0200)

> From: Luis Machado <luisgpm@linux.vnet.ibm.com>
> Date: Fri, 18 Jan 2008 14:38:02 -0200
> 
> > Sorry for not noticing earlier, but why do we need target description
> > feature for *pseudo* registers?
> > 
> 
> The purpose of this feature in the target description is to tell GDB
> which targets support these pseudo-registers, so we're sure that they
> won't appear on other ppc32 targets that do not support it.

But they're pseudo-registers; no target "supports" them because
they're not real registers.  Are you trying to say that some targets
have hardware support for decimal floating point, and you want to make
sure that these pseudo registers only show up on targets that have
such hardware support?  If so I'd appreciate it if you could change
the comments to reflect that.

There are no software implementations that use the floating-point
registers in the same way as the hardware implementation does?


  reply	other threads:[~2008-01-18 17:20 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 [this message]
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
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=200801181702.m0IH2W0E028191@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.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