[Numpy-discussion] Disabling Extended Precision in NumPy (like -ffloat-store)
Charles R Harris
Wed Apr 21 10:07:59 CDT 2010
On Wed, Apr 21, 2010 at 8:47 AM, Adrien Guillon <firstname.lastname@example.org>wrote:
> Hello all,
> I've recently started to use NumPy to prototype some numerical
> algorithms, which will eventually find their way to a GPU (where I
> want to limit myself to single-precision operations for performance
> reasons). I have recently switched to the use of the "single" type in
> NumPy to ensure I use single-precision floating point operations.
> My understanding, however, is that Intel processors may use extended
> precision for some operations anyways unless this is explicitly
> disabled, which is done with gcc via the -ffloat-store operation.
> Since I am prototyping algorithms for a different processor
> architecture, where the extended precision registers simply do not
> exist, I would really like to force NumPy to limit itself to using
> single-precision operations throughout the calculation (no extended
> precision in registers).
> How can I do this?
Interesting question. But what precisely do you mean about limiting? Do you
want *all* floating calculations done in float32? Why does the extended
precision cause you problems? How do the operations of the GPU conflict with
those of the intel FPU? So on an so forth.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion