GCC Turns 25 192
eldavojohn writes "With the release of GCC 4.7.0, the venerable and stalwart constant that is the GNU Compiler Collection turns twenty five. More ISO standards and architectures supported with this release and surely more memories to come from the compiler that seems to have always been."
Re:lolcompilers (Score:5, Insightful)
Thanks gcc! (Score:5, Insightful)
You youngin' have no idea of what kind of crap for compilers we had to put up with until gcc.
25 years of compilation with gcc!
Re:And showing every bit of its age too, apparentl (Score:5, Insightful)
<br><br>
NXP recommends GCC (Code Red IDE which is Eclipse-based), and ST recommends Keil, for their ARM micros. Just FYI.
<br><br>
Good luck on your school project.
Re:And showing every bit of its age too, apparentl (Score:5, Insightful)
Re:And showing every bit of its age too, apparentl (Score:2, Insightful)
Well, one thing that's happened to me an awful lot is that GCC seems to generate smaller *and* faster code when using -Os rather than -O3. That it'd be smaller was no surprise to me, but the speed-up was. (For reference, I'm using an IA32 2 GHz CPU with 1.5 GB of RAM.)
Fewer cache misses, maybe?
Re:Thanks gcc! (Score:5, Insightful)
Having competing products (browsers, compilers, operating systems, ...) help keep those products from stagnating and help push all involved products to improving. It also helps prevent people being reliant on specific compiler/browser/office suite behaviour. GCC is not a "crap compiler", just like Firefox is not a "crap browser". That is not saying that GCC is issue free, nor that it has improved in part as a result from LLVM/Clang. Likewise, LLVM/Clang is not the panacea of compilers.
Competition on a level playing field is a good thing.
Re:Thanks gcc! (Score:2, Insightful)
The guy in that second link doesn't sound very pissed off. And clang definitely has WAY better error messages and analysis/refactoring available to it. As for the codegen, it beat GCC by a wide margin when it first came around, but GCC seems to have surpassed it again in more recent versions.
But the key for any commercial entity is that clang beats the pants off any GPLv2-licensed compiler, and GPLv3-licensed code is pretty much irrelevant to most applications. So GCC is doing a great job for the insulated linux world, and hopefully clang can catch back up to offer the rest of us a better choice.
Re:Thanks gcc! (Score:5, Insightful)
How exactly GPLv3 on the _compiler_ stops you from doing anything? It has only one effect: ensures the toolchain stays usable for everyone.
Thank you gnu (Score:5, Insightful)
Now, get off my lawn.
Re:It's hard work being a JavaScript Rockstar. (Score:2, Insightful)
It is has been intentional been feature ridden....
WTF?
I think it's a non-proofread approximation of saying "Javascript has lots of language features, many of which are redundant". The implication being that the language is bigger than it needs to be and so is more complex and difficult to read than it should be.
All ugly languages have this problem, the lack of orthogonality results in massive numbers of anti-patterns (see Perl as the classic default example, C++ is another).
Re:Thanks gcc! (Score:3, Insightful)
Richard Stallman would point out how he has been talking about the dangers of secure boot and software patents for years, and how Theo just now figured out that those things might be a problem. Then we would watch two grown men stare and gleer at each other.
Re:Microsoft bought and rebranded Lattice C. (Score:3, Insightful)
Oh, come on. I despise Microsoft as much, or more, than anyone here. But how does freely selling something for an agreed-on price of $75K make SCP a victim, no matter what Microsoft may have done with their purchase subsequently?
If I sell my house for $200K, and the buyer subsequently resells it some time later for $300K, can I be a victim too? Is no one an adult any more, capable of making decisions and accepting the consequences, for better or worse? Let's grow up, shall we?
Re:Thanks gcc! (Score:4, Insightful)
Imagine that your favorite text editor uses Clang's own parser to generate its syntax highlighting and check for errors as you type. With the GPL, your editor would likely have to be released under the GPL.
If your editor is modular and you include a plug-in for this function, then only the plug-in needs to be GPL'd. Your program doesn't, because it doesn't depend on it to function, it only adds additional functionality.