From: Andreas Schwab <schwab@suse.de>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Long double support on m68k
Date: Wed, 25 Jul 2001 09:05:00 -0000 [thread overview]
Message-ID: <jevgkhm1tb.fsf@sykes.suse.de> (raw)
In-Reply-To: <3B5EE8BE.1040508@cygnus.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
Andrew Cagney <ac131313@cygnus.com> writes:
|> > Yes (if they support the fpu at all).
|> > |> So, if a target's raw FP registers are in the correct format for
|> > |> REGISTER_CONVERT* then they are also in the correct format for this change
|> > |> and such targets will continue to work. If a target's raw FP registers
|> > |> were not in the correct format then, that target is already broken and
|> > |> this change doesn't make things better or worse.
|> > Yes. There is only one floating point format for the m68k fpu. The
|> > previous version already assumed floatformat_m68881_ext, this patch just
|> > removes the conversion, and makes the raw format avaliable to gdb.
|>
|>
|> The other thing it affects is `sizeof (long double)`. For GCC, at least,
|> is m68k's `sizeof (long double)` 12?
Yes, of course. That's why I started with this patch, a testsuite failure
indicated that something was wrong.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-07-25 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 7:30 Andreas Schwab
2001-07-24 8:58 ` Andrew Cagney
2001-07-24 9:13 ` Andreas Schwab
2001-07-24 15:12 ` Andrew Cagney
2001-07-25 1:17 ` Andreas Schwab
2001-07-25 8:42 ` Andrew Cagney
2001-07-25 9:05 ` Andreas Schwab [this message]
2001-07-25 15:47 ` Andrew Cagney
2001-07-26 1:43 ` Andreas Schwab
2001-07-26 6:36 ` Andrew Cagney
2001-07-28 13:03 ` Andrew Cagney
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=jevgkhm1tb.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ac131313@cygnus.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