Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "J. Johnston" <jjohnstn@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Richard Henderson <rth@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: fix ia64 long double support
Date: Sat, 06 Dec 2003 00:18:00 -0000	[thread overview]
Message-ID: <3FD12055.2000605@redhat.com> (raw)
In-Reply-To: <1031205051806.ZM9509@localhost.localdomain>

Kevin Buettner wrote:
> On Dec 4,  8:54pm, J. Johnston wrote:
> 
> 
>>Richard Henderson wrote:
>>
>>>On Thu, Dec 04, 2003 at 05:37:41PM -0500, J. Johnston wrote:
>>>
>>>
>>>>	* ia64-tdep.c (ia64_gdbarch_init): Set up the gdbarch long double
>>>>	format to be the i387 extended float format which is used for
>>>>	long double's in memory.
>>>
>>>This is os specific.  HPUX uses ieee quad format.
>>>
>>>r~
>>>
>>
>>The Intel doc doesn't differentiate for OS.  Kevin, is this something we should 
>>account for by calling a function in a native tdep file?
> 
> 
> Hmm.  I suppose we could introduce an ia64-linux-tdep.c (with the
> appropriate osabi machinery) to set this for linux.  If it was ever
> made to work with hpux, there'd be an ia64-hpux-tdep.c file which
> would set it to IEEE quad format.
> 
> If you feel up to this, go ahead.  Otherwise, just add a comment
> to ia64-tdep.c which indicates that the setting is Linux specific
> and that other OSes may use other types.  The comment should also
> indicate the correct way that it should be handled (via an OS-specific
> tdep.c file.)
> 
> Kevin
>

I have added a comment and checked the code in.

Thanks,

-- Jeff J.



  reply	other threads:[~2003-12-06  0:18 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 [this message]
2003-12-05  1:19 ` Kevin Buettner
2003-12-05  1:52   ` J. Johnston
2003-12-05  5:13     ` Kevin Buettner

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=3FD12055.2000605@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.com \
    --cc=rth@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