From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) by sourceware.org (Postfix) with ESMTPS id 68D3E3858C83 for ; Thu, 10 Mar 2022 17:27:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 68D3E3858C83 Received: by mail-io1-xd2f.google.com with SMTP id r11so7261300ioh.10 for ; Thu, 10 Mar 2022 09:27:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=E9bz/3CWt6vBp262fXNvHoqQifRDKHbJDHotuopRejw=; b=Wxr/zw+EBld8KzX5mIzJpqDTss9QsLXZH1ghz8MDAJ2zE3gMCOFK7Sdfec+aFszUDc GpJJeBAlSdCQYBs3ZADNUHQxtI3ZQERG8tq2TlQGyWxYiviPNOQGQ36iDmb0t51C5Yg5 BLr1piKYFjHgulTO73McFuZlJzHbFChhZADuHhB4cBPAYZGknCmXfZAuTmAHHxyzKlG1 6Pm2rc9pULHond5uJkXNyPwKSrGUKbe/u/3jYpkqqsKTVp7+6dw5Avt4qSes1dBlyJjJ A6Ll4EM/Yy0Q5JUbnYcWED9MHGVkgoJoBc0SoqzeQTPh3/RykoXN1XgOXyx4GZbHHqkV VYxw== X-Gm-Message-State: AOAM530ATIxK3oPyRyFLKrNpsAgZm+nMKVcu+eyw4MMCbdExulYmwp1G KT68x/BKnxUmlCSNgfmpjJwfHQ== X-Google-Smtp-Source: ABdhPJzPwBmDGLECuxanlM8ih4/fooINvi8eWeOlDrkrlOe18Z0PC7NZB3qYoE5sSRQxn5uSnWfCJQ== X-Received: by 2002:a5e:a80a:0:b0:645:b477:bc23 with SMTP id c10-20020a5ea80a000000b00645b477bc23mr4622016ioa.191.1646933242720; Thu, 10 Mar 2022 09:27:22 -0800 (PST) Received: from murgatroyd (75-166-141-253.hlrn.qwest.net. [75.166.141.253]) by smtp.gmail.com with ESMTPSA id 7-20020a056e0220c700b002c75f643efesm906483ilq.16.2022.03.10.09.27.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 10 Mar 2022 09:27:22 -0800 (PST) From: Tom Tromey To: Eli Zaretskii Cc: Tom Tromey , aburgess@redhat.com, gdb-patches@sourceware.org Subject: Re: [PATCH] Change how "print/x" displays floating-point value References: <20220217212957.1747537-1-tromey@adacore.com> <874k4xdqwl.fsf@redhat.com> <87k0dsqg47.fsf@tromey.com> <83v8xcyuob.fsf@gnu.org> X-Attribution: Tom Date: Thu, 10 Mar 2022 10:27:21 -0700 In-Reply-To: <83v8xcyuob.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 18 Feb 2022 19:02:44 +0200") Message-ID: <87h785ogzq.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-5.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2022 17:27:24 -0000 >> @item d >> -Print as integer in signed decimal. >> +Regard the bits of the value as an integer, and print the integer in >> +decimal. Eli> What does it mean to "regard the bits of the value as an integer" when Eli> the actual value is not an integer, but, say, a C 'double'? I don't Eli> think I understand what to expect from that, by just reading this Eli> description. Would it be possible to have a more clear text? Here I just copied some existing text in the manual. I'm definitely open to other suggestions. The meaning of it is to take the bytes that constitute the floating-point value, then print those as if they constituted an integer value with the same number of bytes. That is, it shows the raw bytes of the floating-point value. Would it be more clear to say Print the underlying bytes of the value as if they were an integer? Tom