Mark Dickinson <dicki...@gmail.com> added the comment:
Did you have a chance to try a debug build of Python and see if the problem
persists there?
I'm failing to reproduce this in OpenSolaris 2009.06, running in Parallels on a
MacBook Pro (non-debug 32-bit build of Python):
dicki...@eratosthenes:~/release26-maint$ uname -a
SunOS eratosthenes 5.11 snv_111b i86pc i386 i86pc Solaris
dicki...@eratosthenes:~/release26-maint$ cat /etc/release
OpenSolaris 2009.06 snv_111b X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 07 May 2009
dicki...@eratosthenes:~/release26-maint$ ./python
Python 2.6.5+ (release26-maint:82213, Jun 25 2010, 00:52:22)
[GCC 3.4.3 (csl-sol210-3_4-20050802)] on sunos5
Type "help", "copyright", "credits" or "license" for more information.
>>> float.hex(-0.0)
'-0x0.0p+0'
>>> import sys; sys.maxsize
2147483647
The most noticeable difference from the machines you describe here is the
compiler. (Did you build gcc 4.4.4 by hand on these machines, or is there a
package I can download and install somewhere?)
I'd still like to understand *how* the -c99 compiler option affects copysign;
it might help inform a workaround. The library function itself can't know how
you compiled Python, surely? Can you work out what's going on from the
relevant header files?
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue9069>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
