From: Andreas Schwab <schwab@linux-m68k.org>
To: Tom Tromey <tromey@adacore.com>
Cc: Andrew Burgess <aburgess@redhat.com>,
Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Change how "print/x" displays floating-point value
Date: Thu, 10 Mar 2022 19:23:35 +0100 [thread overview]
Message-ID: <87ilslll94.fsf@igel.home> (raw)
In-Reply-To: <87czitogv6.fsf@tromey.com> (Tom Tromey's message of "Thu, 10 Mar 2022 10:30:05 -0700")
On Mär 10 2022, Tom Tromey wrote:
>>>>>> "Andreas" == Andreas Schwab <schwab@linux-m68k.org> writes:
>
>>> +print
>>> + Printing of floating-point values with base-modifying formats like
>>> + /x has been changed to display the underlying bytes of the value in
>>> + the desired base. This was GDB's documented behavior, but was never
>>> + implemented correctly.
>
> Andreas> How does that handle padding?
>
> I don't know, can you say more?
It is part of the underlying bytes.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-03-10 18:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 21:29 Tom Tromey via Gdb-patches
2022-02-17 23:17 ` Andrew Burgess via Gdb-patches
2022-02-18 16:44 ` Tom Tromey via Gdb-patches
2022-02-18 17:02 ` Eli Zaretskii via Gdb-patches
2022-03-10 17:27 ` Tom Tromey via Gdb-patches
2022-03-10 17:54 ` Eli Zaretskii via Gdb-patches
2022-03-10 19:19 ` Tom Tromey via Gdb-patches
2022-02-18 17:41 ` Andreas Schwab
2022-02-19 10:05 ` Andrew Burgess via Gdb-patches
2022-03-10 17:30 ` Tom Tromey via Gdb-patches
2022-03-10 17:30 ` Tom Tromey via Gdb-patches
2022-03-10 18:23 ` Andreas Schwab [this message]
2022-03-10 20:39 ` Tom Tromey via Gdb-patches
2022-03-10 20:53 ` Andreas Schwab
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=87ilslll94.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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