Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: fix ia64 long double support
Date: Fri, 05 Dec 2003 05:13:00 -0000	[thread overview]
Message-ID: <1031205051254.ZM9498@localhost.localdomain> (raw)
In-Reply-To: "J. Johnston" <jjohnstn@redhat.com> "Re: [RFA]: fix ia64 long double support" (Dec  4,  8:52pm)

On Dec 4,  8:52pm, J. Johnston wrote:

> > So what happens when we try to print a long double in a register?
> 
> The routine ia64_register_type() returns builtin_type_ia64_ext for the 
> floating-point registers which is the 82-bit register variant.

Okay, cool.

(The patch is still approved.)

Thanks,

Kevin


      reply	other threads:[~2003-12-05  5:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 22:37 J. Johnston
2003-12-05  0:50 ` Richard Henderson
2003-12-05  1:54   ` J. Johnston
2003-12-05  5:18     ` Kevin Buettner
2003-12-06  0:18       ` J. Johnston
2003-12-05  1:19 ` Kevin Buettner
2003-12-05  1:52   ` J. Johnston
2003-12-05  5:13     ` Kevin Buettner [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=1031205051254.ZM9498@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@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