all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Schierl <schierlm@gmx.de>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Procps in core-updates
Date: Mon, 20 Mar 2023 21:02:01 +0100	[thread overview]
Message-ID: <83194a1d-4589-aed9-09a3-5d1495d06699@gmx.de> (raw)
In-Reply-To: <ZBhzvdPsXmFnrCkr@jurong>

Hello Andreas,

Am 20.03.2023 um 15:54 schrieb Andreas Enge:
> Hello Michael,
>
> I am attaching a simplified C file and the corresponding assembly
> output; which I cannot read, but there are differences between the two
> invocations of fprintf.

Seems that you accidentally attached the object file (binary) instead of
the assembly output. :-)

> The weirdest thing is that actually the value is the integer 123. So it
> should be stored in any kind of register exactly.

123 as a normalized binary floating point number would be

1.921875 × 2⁶

and you would have to represent the mantissa in binary (1.111011₂).
Still this should fit into most floating point registers easily.

But possibly the value computed by the algorithm of parsing the number
resulted in e.g.

1.111011000000000000000000000000000000000000000000000001011₂ × 2⁶

which is still 123 when converted back to a 52-bit mantissa, but
something ever so slightly larger when treated as an 80-bit float with
64 bits mantissa.

Or maybe I'm missing something :-)


Regards,


Michael


  reply	other threads:[~2023-03-20 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 12:32 Procps in core-updates Andreas Enge
2023-03-18 17:38 ` Leo Famulari
2023-03-18 17:44   ` Andreas Enge
2023-03-19 17:36 ` Michael Schierl
2023-03-20 14:54   ` Andreas Enge
2023-03-20 20:02     ` Michael Schierl [this message]
2023-03-20 21:25       ` Andreas Enge
2023-03-19 17:49 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-19 19:22   ` Kaelyn

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=83194a1d-4589-aed9-09a3-5d1495d06699@gmx.de \
    --to=schierlm@gmx.de \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.