Linked by Thom Holwerda on Thu 7th Oct 2010 19:10 UTC, submitted by tyrione
Thread beginning with comment 444479
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2006-01-24
Well, GCC is a compiler collection (which is what the CC stands for). GCC has a fair number of supported languages and target architectures.
http://en.wikipedia.org/wiki/GNU_Compiler_Collection#Languages
http://en.wikipedia.org/wiki/GNU_Compiler_Collection#Architectures
In contrast, LLVM front ends actually appear to come from GCC:
http://en.wikipedia.org/wiki/Low_Level_Virtual_Machine#Front_ends
... whereas I can't find any information on what machine architectures are supported, so I would presume it is only x86 and x86_64.
So in terms of at least the metric "what it supports", GCC takes quite some beating.
Yes gcc supports more architectures and the same goes for languages and I doubt this is going to change anytime soon since llvm's language/architecture support direction is largely that of Apple's which shows in their clang/llvm's history c->objc->c++ .
As for frontends, llvm was piggybacking on gcc with llvm-gcc for quite some time while clang was maturing but llvm-gcc has been deprecated now for the dragonegg plugin which allows you to use llvm as a backend for gcc (from gcc 4.5 onwards iirc).