[Python-bugs-list] [ python-Bugs-775892 ] test_coercion failing on Panther

[SourceForge.net]

Bugs item #775892, was opened at 2003-07-22 23:16
Message generated for change (Comment added) made by jackjansen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=775892&group_id=5470

Category: Macintosh
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Jack Jansen (jackjansen)
Assigned to: Jack Jansen (jackjansen)
Summary: test_coercion failing on Panther

Initial Comment:
Test_coercion is failing on Panther. All the failures have the 
same form: the output is (XXX-0j) in stead of the expected 
(XXX+0j).

----------------------------------------------------------------------

>Comment By: Jack Jansen (jackjansen)
Date: 2003-07-24 00:19

Message:
Logged In: YES 
user_id=45365

Fixed in configure.in rev. 1.427, configure rev. 1.416.

----------------------------------------------------------------------

Comment By: Jack Jansen (jackjansen)
Date: 2003-07-23 11:04

Message:
Logged In: YES 
user_id=45365

Edward had also come across the bug, and suggests the following:

The workaround is to add the complier flag "-mno-fused-madd".  
This works for Jaguar and Panther, but I don't know how far back 
it may go.  My test report for c1 uses this flag.

The question is: do we fix this for rc2 or leave it?

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2003-07-22 23:29

Message:
Logged In: YES 
user_id=31435

Ignore it -- the sign of a float 0 is more accidental than not.  
If the compiler has a switch to disable generation of fused 
multiply-add instructions, the failure will probably go away.

After 2.3, we should rewrite the test so that "sign of 0" cases 
aren't even tried anymore.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=775892&group_id=5470