From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: arm-tdep.h:#define FP_REGISTER_VIRTUAL_SIZE 8?
Date: Thu, 18 Apr 2002 03:00:00 -0000 [thread overview]
Message-ID: <200204180959.KAA16776@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 17 Apr 2002 16:41:08 EDT." <3CBDDDE4.5060708@cygnus.com>
> Hmm,
>
> Another think-o? The arm (according to FP_REGISTER_RAW_SIZE) has 12
> byte registers. Their type is builtin_type_arm_ext and that ``virtual
> type'' has a size of 12 bytes.
>
> I suspect this is another hang-over from when Arm was converting RAW FP
> registers (badly) into host FP values. Hmm, if that macro goes, it
> looks like all the ..._size() functions can be reduced to:
> TYPE_LENGTH(type).
>
> (Back to looking at Arm's ON_STACK).
Not sure. It's more of the complete mess that is the FPA. The world
would be all so much easier if I could just rip out FPA support
entirely.... ;-)
R.
prev parent reply other threads:[~2002-04-18 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 13:41 Andrew Cagney
2002-04-18 3:00 ` Richard Earnshaw [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=200204180959.KAA16776@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=gdb@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