From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 27 Feb 2014 07:09:24 -0500
To: 9fans@9fans.net
Message-ID: <817c1134cd276abf444e8f03633b63d4@mikro.quanstro.net>
In-Reply-To: <015a7a246411aad9175339f972052f20@quintile.net>
References: <015a7a246411aad9175339f972052f20@quintile.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] IEEE floats
Topicbox-Message-UUID: be7149fa-ead8-11e9-9d60-3106f5b1d025

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().
>=20
> 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 =E2=89=A1 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