EsoErik

Python built with GCC produces correct results; Python built with a super ultra expensive vendor compiler produces bad results.  Man, this really takes me back...  The last time I dealt with a GCC vs vendor compiler correctness situation on a UNIX-like system was at least 15 years ago, with MIPS Pro, which I had modified to avoid time consuming license checks at each invocation.  After restoring the unmodified version and instead cracking the FlexLM license server (yeah, sorry, as a student, I didn't have $16,995.00 to blow on shit that doesn't even fucking work, and cracking software on IRIX was hilariously easy - the license server was such a piece of junk you could use it from the guest account to overwrite any file on the entire system by manipulating the log path environment variable), the issue remained.  So, the problem really was MIPS Pro, probably.  This time around, in our modern world of bullshit, who even knows or cares?  GCC works.  Into the trash the Intel Compiler goes...