t( FE_DIVBYZERO)
to make gcc complain of "inconsistent operand constraints in an `asm'".
Is there anyone who can parse that hornet's nest of a definition?
Vincent Broman
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
ine asm or anything.
I don't understand "__THROW".
I'm afraid I would need to find the asm code involved, before I could
see what "operand constraints" are "inconsistent".
Any hints where to look?
Any way to make the call go to a nice simple library instead?
n implicit scale, and you only want to do integer arithmetic
to save time/space, not because it is a good conceptual fit to the problem.
In an interpreted language like Python, fixed point seems like
a strange bird. I just use complex floats and a fast library.
Vincent Broman
Harris asked about long doubles.
On my YDL, SIZEOF_LONG_DOUBLE and sizeof( long double) were both 8.
Vincent Broman
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
nd cos which I checked.
Harris:
> What is the PPC model number?
The CWC VSS4 contains four powerpc G4's, the 7400.
Vincent Broman
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
ssage; I suspect there is some long complicated
cpp macro or asm statement in some include file which
I don't find.
Has anyone tried building numpy on Yellow Dog Linux or on a PowerPC with gcc?
Vincent Broman
[EMAIL PROTECTED]
___
Numpy-discussion mail
