From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id A58UAVQ7KmJTGwAAWB0awg (envelope-from ) for ; Thu, 10 Mar 2022 12:54:28 -0500 Received: by simark.ca (Postfix, from userid 112) id E5BDE1F3CA; Thu, 10 Mar 2022 12:54:27 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 4DCAE1EA69 for ; Thu, 10 Mar 2022 12:54:27 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 93595385840B for ; Thu, 10 Mar 2022 17:54:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 93595385840B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1646934866; bh=lp2XXU6rkmVJUEx+SQICtpA1SjshmvIxAI/85u+IiKc=; h=Date:To:In-Reply-To:Subject:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=sOQWkh/r1gOTxM2ztUj1OvcmIsk+5C28LGnGR5mIQdwLmhpokgo8R/O1NbNwLV5dw iX0NuxQvEhzHpvm9MCyndvIYJmkfjhyBzDVWJJYzUh0cpSmxBK+IsV3cbfL0CC3InR LxScsOph9VJjLbWOx5Xbypi9grgCkJwxZe3t75lM= Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id A18903858D39 for ; Thu, 10 Mar 2022 17:54:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A18903858D39 Received: from [2001:470:142:3::e] (port=60558 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nSMzI-0000U0-6z; Thu, 10 Mar 2022 12:54:08 -0500 Received: from [87.69.77.57] (port=3239 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nSMzG-0006A5-1m; Thu, 10 Mar 2022 12:54:07 -0500 Date: Thu, 10 Mar 2022 19:54:05 +0200 Message-Id: <831qz9els2.fsf@gnu.org> To: Tom Tromey In-Reply-To: <87h785ogzq.fsf@tromey.com> (message from Tom Tromey on Thu, 10 Mar 2022 10:27:21 -0700) 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> <87h785ogzq.fsf@tromey.com> 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: , From: Eli Zaretskii via Gdb-patches Reply-To: Eli Zaretskii Cc: aburgess@redhat.com, gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" > From: Tom Tromey > Cc: Tom Tromey , aburgess@redhat.com, > gdb-patches@sourceware.org > Date: Thu, 10 Mar 2022 10:27:21 -0700 > > 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? Yes. I think I would even lose the "as if they were an integer" part. Or maybe something like this: Print the binary representation of the value in decimal.