From: Paul Brook <paul@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Floating point types in target descriptions
Date: Fri, 13 Apr 2007 12:48:00 -0000 [thread overview]
Message-ID: <200704131348.10042.paul@codesourcery.com> (raw)
The patch below adds ieee_single and ieee_double predefined types for use in
XML target descriptions. These are needed to describe vector types with
floating point elements.
I considered using "float"/"double" and/or "float32"/"float64". However the
former are ambiguous with the "float" register type, and the latter don't
really tell you want you're getting. If targets need non-ieee types they can
add them like arm_fpa_ext.
Ok?
Paul
2007-04-13 Paul Brook <paul@codesourcery.com>
* target-descriptions.c (tdesc_named_type): Add ieee_single and
ieee_double.
* doc/gdb.texinfo: Document ieee_single and ieee_double target types.
Index: gdb/doc/gdb.texinfo
===================================================================
--- gdb/doc/gdb.texinfo (revision 168411)
+++ gdb/doc/gdb.texinfo (working copy)
@@ -26070,6 +26070,12 @@ pointers; printing a code pointer conver
address. The stack pointer and any dedicated address registers
may be marked as data pointers.
+@item ieee_single
+Single precision IEEE floating point.
+
+@item ieee_double
+Double precision IEEE floating point.
+
@item arm_fpa_ext
The 12-byte extended precision format used by ARM FPA registers.
Index: gdb/target-descriptions.c
===================================================================
--- gdb/target-descriptions.c (revision 168411)
+++ gdb/target-descriptions.c (working copy)
@@ -409,6 +409,12 @@ tdesc_named_type (const struct tdesc_fea
if (strcmp (id, "uint64") == 0)
return builtin_type_uint64;
+ if (strcmp (id, "ieee_single") == 0)
+ return builtin_type_ieee_single;
+
+ if (strcmp (id, "ieee_double") == 0)
+ return builtin_type_ieee_double;
+
if (strcmp (id, "arm_fpa_ext") == 0)
return builtin_type_arm_ext;
next reply other threads:[~2007-04-13 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 12:48 Paul Brook [this message]
2007-04-13 13:53 ` Daniel Jacobowitz
2007-04-14 0:32 ` Paul Brook
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=200704131348.10042.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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