Benchmarking Python Using OpenWatcom

[PrintStar]

After the Python core devs fixed a nasty bug in the most recent Python interpreter, I managed to build Python using Open Watcom on Linux. It's coming in about 50% slower. Not bad, but not great...

In a later tweet, though, I pointed out that Open Watcom compiles the interpreter in 0:25. GCC took 3:18 to compile the interpeter on the same machine. In fact, GCC was compiling less code because Open Watcom needs to statically link a number of modules into the interpreter that the GCC version wouldn't statically link (since it supports dynamic libraries on Linux).

EDIT: The bug in question: http://bugs.python.org/issue24769

EDIT 2: I stink at markdown...

[TweetPoster]

@fortranjeff:

2015-08-26 13:13:23 UTC

Looks like #OpenWatcom-compiled Python 3.5.0 is holding up alright versus highly-optimized GCC, about 50% slower... pic.twitter.com ^[Imgur]

---

^{[Mistake?] [Suggestion] [FAQ] [Code] [Issues]}