From: dave.l@mac.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fun and scary evil C code
Date: Thu, 20 Dec 2007 00:33:50 +0000 [thread overview]
Message-ID: <3FA5A9CA-EE09-4FDB-A9AA-118E3E8A3AB6@mac.com> (raw)
In-Reply-To: <67C6BAFA-908C-4756-848F-4D65095913EB@mac.com>
> As far as I can see,
> they're assuming that double is IEEE 754 and that you can
> rip apart such a representation on an random-endian machine
> and re-assemble it on an any other random-endian machine.
I lied.
They're actually using that stuff to pick apart the (presumed IEEE 754)
doubles into exponent, mantissa, ...
My questions still stand ...
Also, that file is such a tangled nest of ifdefs ...
is anyone sure whether (and if so, when) that code is invoked?
DaveL
next prev parent reply other threads:[~2007-12-20 0:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 15:15 David Leimbach
2007-12-19 20:37 ` Russ Cox
2007-12-19 22:32 ` Robert William Fuller
2007-12-19 22:38 ` erik quanstrom
2007-12-19 22:51 ` Bakul Shah
2007-12-20 0:18 ` dave.l
2007-12-20 0:33 ` dave.l [this message]
2007-12-20 0:51 ` erik quanstrom
2007-12-20 9:29 ` roger peppe
2007-12-20 13:02 ` erik quanstrom
2007-12-20 16:29 Russ Cox
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=3FA5A9CA-EE09-4FDB-A9AA-118E3E8A3AB6@mac.com \
--to=dave.l@mac.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).