GCC 4.9 Diagnostics Will Begin Playing With Colors
Phoronix: GCC 4.9 Diagnostics Will Begin Playing With Colors
While GCC 4.8 was released less than two months ago and GCC 4.9 isn't likely to surface until 2014, there's already a new feature to the next major update of the GNU Compiler Collection. GCC 4.9 introduces support for colored outputs in debugging...
Origin of colour ?
Well, technically colour output in GCC has been available for ages, thanks to tools like colorgcc - which post-processed and colorized gcc/g++ messages (actually since even before someone start to think about creating llvm), but were a 3rd party separate layer/wrapper (à la distcc, ccache, etc.)
Originally Posted by phoronix
The novelty, as far as I've understood, is that GCC is baking better support for error-reporting directly into core GCC itself, by exporting more of its internal data (à la LLVM) instead of post-processing the output through an external script.
Good with some healthy competition!
It's funny how people who requested this in the past, or even provided patches, were ridiculed and laughed at.
Not sure if you were being sarcastic or not RealNC, but i'll assume you werent and actually answer the question: LLVM.
Originally Posted by RealNC
People can hate on the license all they want (personally it doesnt bug me too much but thats not the point) LLVM is producing similar-quality binaries, with better diagnositcs, with better integration to IDE, with faster compiles at less memory, AND a cleaner codebase. GCC could laugh at Clang for a little while, but Clang caught up while GCC stayed lazy. Now (4.7 and 4.8) they realized they really do need to get their shit together. If LLVM has a feature, then GCC wants the same feature. If GCC has a feature, LLVM wants it.
Quite frankly...I think LLVM is gonna win out, and the GCC developers have already said why:
LLVM has a better architecture and a cleaner code base. GCC wants that architecture now, but they cant GET that architecture because it would mean shelving GCC development for like a year while a small team refactors the entire codebase, and thats not feasible. So any changes to GCC are going to have to be done by either 1) a lone developer or two who integrates the changes back in via a massive patch or 2) Much smaller bit by bit conversion from one architecture to another that could be more error / bug prone way, but its the easier to get done with the whole community involved
When it does, I'll have a beard.
Originally Posted by Ericg
When C11 introduced variable length arrays as mandatory, the pretence of keeping backward compatibility has dissipated to the point where the decision to self compile GCC using the C++ compiler was barely debated. A few highlights hardly seem important at this point...
Originally Posted by RealNC
I suspect after C++14 file-system libraries, all hell will break loose and some radical changes will start happening all over the board...
Last edited by c117152; 05-05-2013 at 01:11 AM.
Originally Posted by c117152
Can you point out where VLA's were made mandatory? LLVM has been submitting patches to the kernel to remove VLA's and if you compile with GCC with "-pedantic" aka: no non standard extensions, it refuses to compile a VLA
Tags for this Thread