I see. Always poignant to hear these kinds of stories. I'm curious as to whether interrupt handling was done underneath the multiprocessing layer or whether in

I see. Always poignant to hear these kinds of stories. I'm curious as to whether interrupt handling was done underneath the multiprocessing layer or whether interrupts were just hammering the pipeline design. (I assume by "an interrupt" you're referring to slowdown within the fraction of a second after a given interrupt occurred, within the context of floods of interrupts interspersed between instructions?) Very cool to hear that Intel snapped up what you eventually managed to ship, FWIW - and that you were able to pivot in the way you did. Also interesting to hear about Opteron use in the field, my experience is only with tracking the consumer sector. Also, the "GPLed SGI compiler" part you mentioned caught my eye and led me to the EKOpath compiler, and particularly its OSS release in 2011: http://web.archive.org/web/20110616135434/http://pathscale.com/ekopath4-open-source-announcement http://web.archive.org/web/20110616135434/http://pathscale.c... After some floating back and forth I found https://www.phoronix.com/forums/forum/software/general-linux-open-source/880291-what-happened-to-pathscale-s-open-source-path64-compiler-suite?p=880485 https://www.phoronix.com/forums/forum/software/general-linux... which a) mirrored my questioning exactly and b) contained a very nice and straightforward answer, so I guess that put closure on that. Really sad that it never really took off though; faster compilers (https://lwn.net/Articles/447541/ https://lwn.net/Articles/447541/ in/from https://lwn.net/Articles/447529/ https://lwn.net/Articles/447529/) are always something I'm looking for :)