2 ms·
At least as I understand it, "PL/8" had two different components: (a) a compiler suite including an IR, optimizer, backends, frontends for various languages in
by skissane 7y ago
At least as I understand it, "PL/8" had two different components:
(a) a compiler suite including an IR, optimizer, backends, frontends for various languages including Pascal
(b) one of those frontends providing its own PL/I dialect designed for system programming
I think, in sense (b), PL/8 was viewed as an alternative to PL/S, PL/X, etc. PL/8 was used for millicode, and possibly also coprocessors for IO and service functions, whereas PL/X played the same role for the OS proper (at least for MVS / OS/390 / z/OS). Whereas, I think as that paper explains, (a) was at some point retired in favour of writing a GCC frontend for (b), partially because (a) didn't support 64-bit, and I guess reusing GCC was seen as less work than upgrading (a) to have 64-bit support.
I think (a) may have had some shared history with IBM CSet / VisualAge / XL C compilers, in their pre-LLVM form. But, given the later got 64-bit support long before LLVM came along, why was (a) retired for lacking 64-bit support? Pure speculation on my part, but I suspect that there was a fork/divergence at some point, and the PL/8 compiler ended up being a completely different body of code, even if some of it had contributed to IBM's other compilers. (And, that contribution may have been in the form of ideas or concepts rather than actual code.)
(I'm sort of piecing together bits of information IBM has released here, so I may be wildly wrong in my speculations. I've never worked for IBM, so I don't have any inside info on this.)