<story><title>GCC 7 Release Series – Changes, New Features, and Fixes</title><url>https://gcc.gnu.org/gcc-7/changes.html</url></story><parent_chain><item><author>Bino</author><text>If you compare (gcc7 and latest clang), how much in pair is gcc with clang in terms of compilation warnings? (One of the most valuable tool of a compiler). I&amp;#x27;m really happy they are moving in the same direction; I&amp;#x27;ve been worried about gcc.</text></item></parent_chain><comment><author>srean</author><text>For gcc-4.3 this was a no contest, clang was clearly better. However, gcc has made up a lot of ground over the years, to the point that I now consider gcc&amp;#x27;s template based error messaes better. It is very difficult to keep personal judgement and tastes out of the equation so ymmv.&lt;p&gt;If the error message of one is not very illuminating I often try the other compiler on the same piece of code. It is a good practice anyway and I should be doing more of that.&lt;p&gt;One claim that everyone will stand by is that the competition between the two has been a huge help.</text></comment>
<story><title>GCC 7 Release Series – Changes, New Features, and Fixes</title><url>https://gcc.gnu.org/gcc-7/changes.html</url></story><parent_chain><item><author>Bino</author><text>If you compare (gcc7 and latest clang), how much in pair is gcc with clang in terms of compilation warnings? (One of the most valuable tool of a compiler). I&amp;#x27;m really happy they are moving in the same direction; I&amp;#x27;ve been worried about gcc.</text></item></parent_chain><comment><author>lorenzhs</author><text>They&amp;#x27;re both very good now. Sometimes the error messages of one are clearer than the other&amp;#x27;s, sometimes it&amp;#x27;s the other way around. If I don&amp;#x27;t immediately find the cause in a long templatey error, I&amp;#x27;ll just check the other compiler&amp;#x27;s message. Having both messages can be surprisingly helpful :)</text></comment>