Re:LLVM's Clang Successfully Self-Hosts
by krakensden on Friday February 05, 2010 @01:29AM
(#1102895)
I'd argue that there is an age factor at play- GCC is older, designed under different (ie, much more stringent with regards to resources) constraints.
GCC also has a perennial problem attracting and managing developers, which LLVM seems to have avoided.
It's really not the age or resources that hamper it (from experience hacking it). Well, OK, the age does matter -- but only because it's C. It wouldn't have been so bad if they didn't have to reinvent basic things. GCC has its own garbage collector, a set of bizzare hacks to replace inheritance, amongst other atrocities. None of these have to do with resource constraints, and nearly all have to do with the low-level nature of C.
I'm hacking on a compiler written in C, which isn't worse than LLVM: http://libfirm.org
Why do a compiler in C at all? I mean, why should a low-level systems language (that values speed above everything) be particularly suited to transforming programs from one language into another?
Re:LLVM's Clang Successfully Self-Hosts
by nvoorhies on Friday February 05, 2010 @01:04PM
(#1104269)
Because this allows you to compile in places and times where a language with more suitability towards compilation but heavier time or memory needs would be unsuitable.
One example that pops to mind is shader programs on a GPU.
Language features for abstraction and encapsulation are pretty important for something that huge.