public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: aburgess@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Change how "print/x" displays floating-point value
Date: Fri, 18 Feb 2022 19:02:44 +0200	[thread overview]
Message-ID: <83v8xcyuob.fsf@gnu.org> (raw)
In-Reply-To: <87k0dsqg47.fsf@tromey.com> (message from Tom Tromey via Gdb-patches on Fri, 18 Feb 2022 09:44:24 -0700)

> Date: Fri, 18 Feb 2022 09:44:24 -0700
> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Tom Tromey <tromey@adacore.com>,
>  Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
> 
> Let me know what you think of this.
> 
> Tom
> 
> commit bb4117440a91bff97483eaab4d12543c9663de09
> Author: Tom Tromey <tromey@adacore.com>
> Date:   Thu Feb 17 13:43:59 2022 -0700

Thanks.  I find the documentation confusing:

>  @item d
> -Print as integer in signed decimal.
> +Regard the bits of the value as an integer, and print the integer in
> +decimal.

What does it mean to "regard the bits of the value as an integer" when
the actual value is not an integer, but, say, a C 'double'?  I don't
think I understand what to expect from that, by just reading this
description.  Would it be possible to have a more clear text?

  reply	other threads:[~2022-02-18 17:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 21:29 Tom Tromey
2022-02-17 23:17 ` Andrew Burgess
2022-02-18 16:44   ` Tom Tromey
2022-02-18 17:02     ` Eli Zaretskii [this message]
2022-03-10 17:27       ` Tom Tromey
2022-03-10 17:54         ` Eli Zaretskii
2022-03-10 19:19           ` Tom Tromey
2022-02-18 17:41     ` Andreas Schwab
2022-02-19 10:05       ` Andrew Burgess
2022-03-10 17:30         ` Tom Tromey
2022-03-10 17:30       ` Tom Tromey
2022-03-10 18:23         ` Andreas Schwab
2022-03-10 20:39           ` Tom Tromey
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=83v8xcyuob.fsf@gnu.org \
    --to=eliz@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).