Re:New SSA Back End for the Go Compiler (2015)
by nickpsecurity on Saturday April 02, 2016 @03:12PM
(#11412862)
Dude is brillaint and did great work. Yet, the Oberons and Pascals compiled so fast my finger was barely off the key when they were done. Even the C/C++ editors werent that fast for Java. Allowed rapid iteration while maintaining mental flow. When done, you turn all the options on with that or a slower compiler to get fastest, production version. This has been true going back to the old, Ceres workstations where commenters here that used them reported instant compiles on CPU's with tens of MHz.
[ Parent
| on HN ]
Re:New SSA Back End for the Go Compiler (2015)
by pcwalton on Saturday April 02, 2016 @03:15PM
(#11412873)
Yes, and they didn't do any optimization. That's not particularly interesting; TCC is there if you want it.
Re:New SSA Back End for the Go Compiler (2015)
by nickpsecurity on Saturday April 02, 2016 @03:22PM
(#11412913)
Barely any. Which leads us to differentiate between iterative and release requirements. Language like Go will kill on the former with Wirth-style compilees. A LLVM extension might have been better for latter. That was my recommendation a while back. Even still, the language is simple enough it should compile faster. Should != will of course.