3 ms·
> Java and C# weren´t even a thing. Was the interview in 2009, or not? That was the Java 6 era. I'm still trying to make sense of "destroyed our ability to ad
by MaxBarraclough 8y ago
> Java and C# weren´t even a thing.
Was the interview in 2009, or not? That was the Java 6 era.
I'm still trying to make sense of "destroyed our ability to advance the state of the art" given that we now have modern Java and C#.
- pjmlp 8y agoYes it was in 2009. What she meant was that the adoption of C kind of destroyed their work doing optimizing compilers since the mid-60's, as C lacked any kind of optimization putting that on the shoulders of developers. It was the years of optimization work in C compilers, specially regarding UB abuse that has kind of matched what they were already doing on mainframes. As mentioned PL/8 was a safe systems programming language used to for IBM's RISC compilers and respective OS. The paper describing the toolchain was implemented and the pluggable optimization passes could be describing LLVM today. So with UNIX's adoption the computing world has spent a couple of decades making C compilers up to date with mainframe optimizers, rebuilding the world instead of carrying on where they already were, hence the "destroyed our ability to advance the state of art".
- MaxBarraclough 8y ago> C lacked any kind of optimization putting that on the shoulders of developers I don't get you. C is a low-level language. Its compilers perform ever more extensive optimisations. These aren't in tension. I don't know much about PL/8, but it sounds like the only reason it was fast was because it specifically targeted a particular RISC machine, and ran fast on that one platform? I don't think I'm being dismissive in saying that's essentially cheating, if we're talking about optimising compilers. Assembly code is fast too, but that's not what we're talking about. A fast high-level language means it can compile down to fast code for any target platform. Back then, all compilers were garbage. That's not C's fault. Could PL/8 compile to high-performance code for other platforms? If not, it's not doing the same thing as C. If yes, I'd like to know what it does differently to C. Other than the considerable issues that arise from pointer aliasing, C is a very optimisable language. It's a good thing that we've evolved beyond building languages specifically for machines, and building machines specifically for languages. > the pluggable optimization passes could be describing LLVM today Except nowhere near as sophisticated, and accomplishing nowhere near as much. I really don't buy this idea that C is somehow a slow high-level language, or that its existence has held-back the field of compiler optimisation. > So with UNIX's adoption the computing world has spent a couple of decades making C compilers up to date with mainframe optimizers, rebuilding the world instead of carrying on where they already were The idea that the optimising compilers of yesteryear were just as impressive as today's optimising compilers, strikes me as simply untrue. Compiler optimisation has been improving steadily for decades. I don't see anything to complain about.
- pjmlp 8y agoWell, we just need to compare how Xerox PARC, IBM and AT&T workstations in 1980 compared against each other. I leave it at that, there are plenty of places to find about history of computing.
- MaxBarraclough 8y agoSure. My knowledge isn't strong there, as you've seen :P Good talking to you.
- mpweiher 8y ago> C is a low-level language. Its compilers perform ever more extensive optimisations. These aren't in tension. Yes they absolutely are. A low-level language has fairly little to get between you and the processor. Extensive optimizations get between you and the processor. https://en.wikipedia.org/wiki/Low-level_programming_language https://en.wikipedia.org/wiki/Low-level_programming_language > Compiler optimisation has been improving steadily for decades. Not all that much. See Proebsting's Law. Also see "The Death of Optimizing Compilers", by D.J. Bernstein https://cr.yp.to/talks/2015.04.16/slides-djb-20150416-a4.pdf https://cr.yp.to/talks/2015.04.16/slides-djb-20150416-a4.pdf