1 message in org.python.python-bugs-list[ python-Bugs-789294 ] Solaris Forte ...
FromSent OnAttachments
SourceForge.netMar 21, 2004 11:46 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[ python-Bugs-789294 ] Solaris Forte 7 &8 bug in test_longActions...
From:SourceForge.net (nore@sourceforge.net)
Date:Mar 21, 2004 11:46:47 am
List:org.python.python-bugs-list

Bugs item #789294, was opened at 2003-08-15 08:24 Message generated for change (Settings changed) made by bcannon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=789294&group_id=5470

Category: Python Interpreter Core Group: Platform-specific

Status: Closed Resolution: Invalid

Priority: 5 Submitted By: Nick Maclaren (nmm1) Assigned to: Nobody/Anonymous (nobody) Summary: Solaris Forte 7 &8 bug in test_long

Initial Comment: Python 2.2.3

This is for information. It is a bug in Sun's Forte 7 and 8 compiler suite, very unlikely to affect most people, and I am pursuing it at low priority with Sun. I am reporting it as it will cause the tests to fail if anyone switches floating-point trapping on.

In PyFloat_FromString in floatobject.c, there is a call to strtod. In test_long, this is supplied with a huge argument. Sun have misunderstood C99 (puke) to state that the wording in Annex F requires strtod to raise an exception if it overflows, and have again misunderstood C99 to mean that implies SIGFPE if trapping is on. I don't blame them for getting confused, but their interpretation is wrong - or, at least that what was stated when C99 was in draft!

Generically, we can expect to see more vendors get confused by C99, and especially by the horrible floating-point changes.

Yuck.

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