[issue7296] OverflowError: signed integer is greater than maximum on mips64

jasper added the comment: FYI, the issue has been fixed now in the mips64 port of OpenBSD by "replacing the previous/old floating point completion code with a C interface to the MI softfloat code, implementing all MIPS IV specified floating point operations." -- _

[issue7296] OverflowError: signed integer is greater than maximum on mips64

Mark Dickinson added the comment: Many thanks for the update. I'll close this as not a Python bug, then. (Unless there's an easy and nonintrusive workaround...) -- resolution: -> wont fix status: open -> closed ___ Python tracker

[issue7296] OverflowError: signed integer is greater than maximum on mips64

Otto added the comment: This problem has been diagnosed as a problem in the mips64 port of OpenBSD. mips64 systems need to emulate some floating point instructions in software, depending on the cpu type. In this case we hit an instruction for which the emulation was incomplete. The floating p

[issue7296] OverflowError: signed integer is greater than maximum on mips64

jasper added the comment: Removing --with-fpectl makes no difference. I'll try the _PyHash_Double-thing later this weekend. -- ___ Python tracker ___ ___

[issue7296] OverflowError: signed integer is greater than maximum on mips64

Mark Dickinson added the comment: Sorry, I'm running out of ideas. The traceback is truly baffling. I'm not sure why you're configuring with --with-fpectl. Does removing this make any difference? Maybe you could also try copying _PyHash_Double into a small test program, calling it with an

[issue7296] OverflowError: signed integer is greater than maximum on mips64

jasper added the comment: this little test program: #include int main(int argc, char*argv[]) { printf("short = %d\n", sizeof(short)); printf("int = %d\n", sizeof(int)); printf("float = %d\n", sizeof(float)); printf("long = %d\n", sizeof(long)); printf("double = %d\n", sizeof(double));

[issue7296] OverflowError: signed integer is greater than maximum on mips64

Mark Dickinson added the comment: Hmm. I don't understand that backtrace at all. It seems to say that the conversion of this particular double value (2.34e17) to long is causing some kind of arithmetic exception. I'd assume overflow, except that the configure script says sizeof(long) == 8, an

[issue7296] OverflowError: signed integer is greater than maximum on mips64

jasper added the comment: After properly compiling with -O0, it actually gets a lot further in the build. It crashes elsewhere though: PYTHONPATH=/usr/obj/ports/Python-2.6.3/fake-sgi/usr/local/lib/python2.6 ./python -Wi -tt /usr/obj/ports/Python-2.6.3/fake-sgi/usr/local/lib/python2.6/compile

[issue7296] OverflowError: signed integer is greater than maximum on mips64

Mark Dickinson added the comment: Thanks for filing the report! Some questions: If you configure with the --with-pydebug option, and also do whatever else (if anything) is necessary to remove the -O2 flag from the compilation steps, does the build failure still occur? What's the minimal Pytho

[issue7296] OverflowError: signed integer is greater than maximum on mips64

jasper added the comment: And the build log on OpenBSD/sgi. -- Added file: http://bugs.python.org/file15301/Python-2.6.3.log ___ Python tracker ___ __

[issue7296] OverflowError: signed integer is greater than maximum on mips64

New submission from jasper : While trying to get Python 2.6 working on OpenBSD/sgi (64-bit port) I ran into the following during build: OverflowError: signed integer is greater than maximum I ran the command that triggered this by hand with -v added: (sgi Python-2.6.3 40)$ export PATH; PATH="`