I mean, none of the optimizations I listed rely on multiple cores.
It’s true that just running parallel compilation jobs on your build machine is a simple way to speed things up, no disagreement, but it’s not like optimizing compilation time isn’t a thing outside of that.
i was thinking more about tooling, most of that stuff didn’t exist as widely as today and you couldn’t really look for it when waiting for a compile either.
Well…the in-compiler time analysis I think wasn’t as good then, though I recall doing my own ad-hoc profiling, logging time for each unit. But the refactoring stuff should be available.
I dunno how far back distcc goes.
checks git repository
The git log goes back to 2008, so almost 20 years, but it’s also talking about release 3.0 then, so there might have been time outside a VCS or with history that didn’t get imported.
I mean, none of the optimizations I listed rely on multiple cores.
It’s true that just running parallel compilation jobs on your build machine is a simple way to speed things up, no disagreement, but it’s not like optimizing compilation time isn’t a thing outside of that.
i was thinking more about tooling, most of that stuff didn’t exist as widely as today and you couldn’t really look for it when waiting for a compile either.
Well…the in-compiler time analysis I think wasn’t as good then, though I recall doing my own ad-hoc profiling, logging time for each unit. But the refactoring stuff should be available.
I dunno how far back
distccgoes.checks git repository
The git log goes back to 2008, so almost 20 years, but it’s also talking about release 3.0 then, so there might have been time outside a VCS or with history that didn’t get imported.
Wikipedia says that
ccachegoes back 24 years.