Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/mips] Fix crash trying to print long double float
Date: Sat, 07 Aug 2004 18:22:00 -0000	[thread overview]
Message-ID: <41151DF9.5000706@gnu.org> (raw)
In-Reply-To: <20040807180927.GA1192@gnat.com>

>>>2004-08-06  Joel Brobecker  <brobecker@gnat.com>
>>>> >
>>>> >        * mips-tdep.c (mips_gdbarch_init): Set size of long double
>>>> >        to 128 bits for N32 and N64 ABIs.
>>>> >
>>>> >Tested on mips-irix. OK to apply?
>>
>>> 
>>> Can you also clone / tweak the relevant floatformat (I'm wondering if it 
>>> should just go in doublest.[hc] and we should stop using floatformat.[ch]).
> 
> 
> Yes. I am planning on doing this tonight. But could this done separately
> from this patch, or do you think it doesn't make sense?

Same patch.

> My other question is: Do we need to take care of the big endian
> convention only, or do we need to look at the LE case as well (I don't
> have a clue as to what is happening in that case :-(, if this ever makes
> any sense).

Just take care of the BE case (set nothing for the LE case).  Now that 
we've stopped the fatal crash this isn't an issue.

Andrew



  reply	other threads:[~2004-08-07 18:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06 18:16 Joel Brobecker
2004-08-06 20:24 ` Andrew Cagney
2004-08-06 20:38   ` Joel Brobecker
2004-08-06 21:03     ` Andrew Cagney
2004-08-07 17:18       ` Andrew Cagney
2004-08-06 20:32 ` Joel Brobecker
2004-08-07 18:01   ` Andrew Cagney
2004-08-07 18:09     ` Joel Brobecker
2004-08-07 18:22       ` Andrew Cagney [this message]
2004-08-08  6:59         ` Joel Brobecker
2004-08-08 16:57           ` Andrew Cagney
2004-08-09  5:46             ` Joel Brobecker

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=41151DF9.5000706@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.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