[Openmcl-devel] addenda RE: non-consing short float trap parameters
janderson at ravenpack.com
Wed Mar 8 03:35:49 PST 2006
thank you for the details.
i keep the contortions for single float arguments.
> -----Original Message-----
> From: Gary Byers [mailto:gb at clozure.com]
> Sent: Wednesday, March 08, 2006 11.09
> To: James Anderson
> Cc: openmcl-devel at clozure.com; Testers
> Subject: Re: [Openmcl-devel] addenda RE: non-consing short float trap
> A value in a PPC floating-point register is maintained as a 64-bit
> double float (regardless of how it got there, e.g., whether it
> was loaded from a 32-bit or a 64-bit memory location or whether it's
> the result of a single- or double-precision arithmetic operation.)
> Valid values that are loaded as IEEE single floats (or which are
> the results of single-precision arithmetic operations) will have
> exponents in the IEEE single float range and will not have as
> much precision in their mantissas as will valid values loaded
> as IEEE double-floats or the results of double-precision operations.
> On Tue, 7 Mar 2006, James Anderson wrote:
> > hello again;
> > ?3 i observe that, if doubles are passed where the interface
> specifies singles,
> > (some of) the operations (appear to) work. ...
> > ...
> > ?3.3 is there any general consensus about whether this is "the
> right thing to
> > do"? is "short-sighted"? is "unsupported"?
> > ...
> > _______________________________________________
> > Openmcl-devel mailing list
> > Openmcl-devel at clozure.com
> > http://clozure.com/mailman/listinfo/openmcl-devel
More information about the Openmcl-devel