From: Aldy Hernandez <aldyh@redhat.com>
To: GCC patches <gcc-patches@gcc.gnu.org>
Cc: Andrew MacLeod <amacleod@redhat.com>, Aldy Hernandez <aldyh@redhat.com>
Subject: [PATCH] Add debug functions for REAL_VALUE_TYPE.
Date: Thu, 22 Sep 2022 18:47:52 +0200 [thread overview]
Message-ID: <20220922164752.2566043-1-aldyh@redhat.com> (raw)
We currently have no way of dumping REAL_VALUE_TYPEs when debugging.
Tested on a gdb session examining the real value 10.0:
(gdb) p min
$9 = {cl = 1, decimal = 0, sign = 0, signalling = 0, canonical = 0, uexp = 4, sig = {0, 0, 11529215046068469760}}
(gdb) p debug (min)
0x0.ap+4
OK for trunk?
gcc/ChangeLog:
* real.cc (debug): New.
---
gcc/real.cc | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/gcc/real.cc b/gcc/real.cc
index 73bbac645d9..a31b256a47b 100644
--- a/gcc/real.cc
+++ b/gcc/real.cc
@@ -1900,6 +1900,22 @@ real_to_decimal (char *str, const REAL_VALUE_TYPE *r_orig, size_t buf_size,
digits, crop_trailing_zeros, VOIDmode);
}
+DEBUG_FUNCTION void
+debug (const REAL_VALUE_TYPE *r)
+{
+ char s[60];
+ real_to_hexadecimal (s, r, sizeof (s), 0, 1);
+ fprintf (stderr, "%s\n", s);
+}
+
+DEBUG_FUNCTION void
+debug (const REAL_VALUE_TYPE &r)
+{
+ char s[60];
+ real_to_hexadecimal (s, &r, sizeof (s), 0, 1);
+ fprintf (stderr, "%s\n", s);
+}
+
/* Render R as a hexadecimal floating point constant. Emit DIGITS
significant digits in the result, bounded by BUF_SIZE. If DIGITS is 0,
choose the maximum for the representation. If CROP_TRAILING_ZEROS,
--
2.37.1
next reply other threads:[~2022-09-22 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 16:47 Aldy Hernandez [this message]
2022-09-23 6:54 ` Richard Biener
2022-09-23 7:01 ` Aldy Hernandez
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=20220922164752.2566043-1-aldyh@redhat.com \
--to=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).