Looking At Changes In the Newest GCC
cyberpead writes "With GCC 4 comes a new optimization framework (and new intermediate code representation), new target and language support, and a variety of new attributes and options. Get to know the major new features and their benefits in this article."
That they were able to reduce it down to just one C. Now it's just GC.
Granted, 4.3.2 is pretty cool, but AFAIK it's not revolutionary wrt earlier 4.* releases
The Raven
I've been using it for a year and a half now.
Wow! With all of that, you'd think I was truly enamored with GCC. Let's just say that when I'm developing software with GCC and my wife walks into the room, I feel a little uncomfortable.
That's a little creepy.
I read that as CCG at first... It sounded pretty good too.
"Common sense will be the death of us all"
TFA says GCC 4.0 was released 2 years ago... yet it's titled "Getting to know GCC 4". I guess the author took his time to "get acquainted". Best not to rush into those sort of things...
I've been stuck on gcc 3.4.3 for a few years now. Fortran 95 here I come!!
Just disrupt the deflector shield with a tachyon burst.
Sure would be nice to have them. I suppose the gcc maintainers would never admit to someone from the openbsd group knowing what they're doing, though.
> That they were able to reduce it down to just one C. Now it's just GC.
The Garbage Compiler? Can't be. That sounds more like something used to compile Microsoft products.
Anybody knows how it compares to LLVM?
Big deal about all this GCC4 stuff, let me know when GCC 4.x becomes available for MingW as an official build (or better yet, when the GCC community stops treating Windows builds of GCC as second class citizens)
How the hell did this make front page news like 3 and a half years too late? Firehose fail.
There is still one major target language missing: XML. Hopefully gccxml will one day be merged into the main source tree.
Theoretical question here:
The diagram in the article shows GCC as a bunch of language front-ends that translate to an intermediate language, then a compiler for that intermediate language that produces the machine code.
Isn't this exactly the architecture of the .NET framework? Language compilers for VB, C#, C++ that compile to intermediate code, then interpreted directly instead of to a static machine-code file?
In other words, could a back-end be developed to change GCC into a universal runtime to replace Java and .NET, while still allowing for programming in everything from F77 to Lisp?
WeRelate.org - wiki-based genealogy