News for hackers. Stuff that matters.
Re:GCC 6.1 Released by jeffdavis on Wednesday April 27, 2016 @12:08PM (#11581688)
1. License. If you are worried about GPL (especially v3), then you are better off with clang.

2. GCC is generally considered to produce better binaries.

3. Smart projects will support both and test with both. Before, even though projects tried to be portable, GCC was the only compiler most developers had available. Now they have two (although clang does try to support almost everything GCC does, so it doesn't say a huge amount about portability).

4. If you want to quickly see whether an optimization was applied (like inlining or loop unrolling), looking at LLVM is more approachable, so clang is nice for that.

Re:GCC 6.1 Released by illivah on Wednesday April 27, 2016 @12:19PM (#11581804)
why would the GPL matter for using gcc? It's not like you're modifying, distributing, and selling forks of gcc, it's just a compiler.
Re:GCC 6.1 Released by sqeaky on Wednesday April 27, 2016 @04:33PM (#11584285)
You are using logic, not all decision makers do. Some hear "GPL" and react, "oh that's the viral license can't use anything with that".
Re:GCC 6.1 Released by jeffdavis on Wednesday April 27, 2016 @05:03PM (#11584534)
See sibling comment.
Re:GCC 6.1 Released by jeffdavis on Wednesday April 27, 2016 @04:56PM (#11584477)
Runtime code generation / JIT.