From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] IEEE floats
Date: Thu, 27 Feb 2014 07:09:24 -0500 [thread overview]
Message-ID: <817c1134cd276abf444e8f03633b63d4@mikro.quanstro.net> (raw)
In-Reply-To: <015a7a246411aad9175339f972052f20@quintile.net>
On Thu Feb 27 06:54:22 EST 2014, steve@quintile.net wrote:
> Porting stuff from the net (under ape) which wants to use IEEE floats.
> i.e. ieee754_float32_t, powf(), fabsf() and log10f().
>
> I could map these to plan9 floats and call the double version
> of the transient functions, but is there a better solution?
plan 9 uses ieee floating point on machines that support it
(all current arches) so ieee754_float32_t ≡ float.
substituting the double version should work.
did they abolish the rule that float is promoted to double
on function call? or is this the equivalent of char fu(char) vs
int fu(int).
- erik
next prev parent reply other threads:[~2014-02-27 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 11:51 Steve Simon
2014-02-27 12:09 ` erik quanstrom [this message]
2014-02-27 12:29 ` Charles Forsyth
2014-02-27 12:45 ` erik quanstrom
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=817c1134cd276abf444e8f03633b63d4@mikro.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).