[committed,2/2] wwwdocs: Document my gcc 8 changes for the website (v2)

Message ID	1522865087-39444-3-git-send-email-dmalcolm@redhat.com
State	New
Headers	show Return-Path: <gcc-patches-return-475859-incoming=patchwork.ozlabs.org@gcc.gnu.org> DomainKey-Signature: a=rsa-sha1; c=nofws; d=gcc.gnu.org; h=list-id :list-unsubscribe:list-archive:list-post:list-help:sender:from :to:cc:subject:date:message-id:in-reply-to:references; q=dns; s= default; b=tvVNzxuqd+U2Rq49UGpSVE2eztrn2n7o6Bm3e0jSJ5vwvfwulx9MB J+JIiEXUCYtxNS1D2Sma83rF9K7Sp9Xfj3LV3Z8EibV0GUB91tdxghsaohEEcM7V F722PjOLIIqsBOEQERdW6bl4ZkEKz258Y6YiTiXfjJuD7ta9xzAf4A= Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk Sender: gcc-patches-owner@gcc.gnu.org From: David Malcolm <dmalcolm@redhat.com> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: gcc-patches@gcc.gnu.org, David Malcolm <dmalcolm@redhat.com> Subject: [committed 2/2] wwwdocs: Document my gcc 8 changes for the website (v2) Date: Wed, 4 Apr 2018 14:04:47 -0400 Message-Id: <1522865087-39444-3-git-send-email-dmalcolm@redhat.com> In-Reply-To: <1522865087-39444-1-git-send-email-dmalcolm@redhat.com> References: <alpine.LSU.2.21.1803182357560.3430@anthias.pfeifer.com> <1522865087-39444-1-git-send-email-dmalcolm@redhat.com>
Series	wwwdocs: Updates for gcc 8 changes (v2) \| expand [0/2] wwwdocs: Updates for gcc 8 changes (v2) [1/2] wwwdocs: Add bin/gcc-color-to-html.py [committed,2/2] wwwdocs: Document my gcc 8 changes for the website (v2)

diff --git a/htdocs/gcc-8/changes.html b/htdocs/gcc-8/changes.html index 707cd4e..bc91156 100644 --- a/htdocs/gcc-8/changes.html +++ b/htdocs/gcc-8/changes.html @@ -183,11 +183,243 @@ a work-in-progress.</h2> is now undefined by default at all optimization levels. Using <code>-fsanitize=signed-integer-overflow</code> is now the preferred way to audit code, <code>-Wstrict-overflow</code> is deprecated.</li> + <li>When reporting mismatching argument types at a function call, the + C and C++ compilers now underline both the argument and the pertinent + parameter in the declaration. +<pre class="blackbg"> +$ gcc arg-type-mismatch.cc +arg-type-mismatch.cc: In function 'int caller(int, int, float)': +arg-type-mismatch.cc:5:24: error: invalid conversion from 'int' to 'const char*' [-fpermissive] + return callee(first, second, third); + ^~~~~~ +arg-type-mismatch.cc:1:40: note: initializing argument 2 of 'int callee(int, const char*, float)' + extern int callee(int one, const char *two, float three); + ~~~~~~~~~~~~^~~ +</pre> + + </li> + <li>When reporting on unrecognized identifiers, the C and C++ compilers + will now emit fix-it hints suggesting <code>#include</code> directives + for various headers in the C and C++ standard libraries. +<pre class="blackbg"> +$ gcc incomplete.c +incomplete.c: In function 'test': +incomplete.c:3:10: error: 'NULL' undeclared (first use in this function) + return NULL; + ^~~~ +incomplete.c:3:10: note: 'NULL' is defined in header '<stddef.h>'; did you forget to '#include <stddef.h>'? +incomplete.c:1:1: ++#include <stddef.h> + const char *test(void) +incomplete.c:3:10: + return NULL; + ^~~~ +incomplete.c:3:10: note: each undeclared identifier is reported only once for each function it appears in +</pre> + +<pre class="blackbg"> +$ gcc incomplete.cc +incomplete.cc:1:6: error: 'string' in namespace 'std' does not name a type + std::string s("hello world"); + ^~~~~~ +incomplete.cc:1:1: note: 'std::string' is defined in header '<string>'; did you forget to '#include <string>'? ++#include <string> + std::string s("hello world"); + ^~~ +</pre> + + </li> + <li>The C and C++ compilers now use more intuitive locations when + reporting on missing semicolons, and offer fix-it hints: +<pre class="blackbg"> +$ gcc t.c +t.c: In function 'test': +t.c:3:12: error: expected ';' before '}' token + return 42 + ^ + ; + } + ~ +</pre> + + </li> + <li>When reporting on missing '}' and ')' tokens, the C and C++ + compilers will now highlight the corresponding '{' and '(' token, + issuing a 'note' if it's on a separate line: +<pre class="blackbg"> +$ gcc unclosed.c +unclosed.c: In function 'log_when_out_of_range': +unclosed.c:12:50: error: expected ')' before '{' token + && (temperature < MIN || temperature > MAX) { + ^~ + ) +unclosed.c:11:6: note: to match this '(' + if (logging_enabled && check_range () + ^ +</pre> + or highlighting it directly if it's on the same line: +<pre class="blackbg"> +$ gcc unclosed-2.c +unclosed-2.c: In function 'test': +unclosed-2.c:8:45: error: expected ')' before '{' token + if (temperature < MIN || temperature > MAX { + ~ ^~ + ) +</pre> + They will also emit fix-it hints. + </li> </ul> <h3 id="cxx">C++</h3> <ul> - <li></li> + <li>When reporting on attempts to access private fields of a class or + struct, the C++ compiler will now offer fix-it hints showing how to + use an accessor function to get at the field in question, if one exists. +<pre class="blackbg"> +$ gcc accessor.cc +accessor.cc: In function 'void test(foo*)': +accessor.cc:12:12: error: 'double foo::m_ratio' is private within this context + if (ptr->m_ratio >= 0.5) + ^~~~~~~ +accessor.cc:7:10: note: declared private here + double m_ratio; + ^~~~~~~ +accessor.cc:12:12: note: field 'double foo::m_ratio' can be accessed via 'double foo::get_ratio() const' + if (ptr->m_ratio >= 0.5) + ^~~~~~~ + get_ratio() +</pre> + + </li> + <li>The C++ compiler can now give you a hint if you use a macro before it + was defined (e.g. if you mess up the order of your <code>#include</code> + directives): +<pre class="blackbg"> +$ gcc ordering.cc +ordering.cc:2:24: error: expected ';' at end of member declaration + virtual void clone() const OVERRIDE { } + ^~~~~ + ; +ordering.cc:2:30: error: 'OVERRIDE' does not name a type + virtual void clone() const OVERRIDE { } + ^~~~~~~~ +ordering.cc:2:30: note: the macro 'OVERRIDE' had not yet been defined +In file included from ordering.cc:5: +c++11-compat.h:2: note: it was later defined here + #define OVERRIDE override + +</pre> + + </li> + <li>The <code>-Wold-style-cast</code> diagnostic can now emit fix-it hints + telling you when you can use a <code>static_cast</code>, + <code>const_cast</code>, or <code>reinterpret_cast</code>. +<pre class="blackbg"> +$ gcc -c old-style-cast-fixits.cc -Wold-style-cast +old-style-cast-fixits.cc: In function 'void test(void*)': +old-style-cast-fixits.cc:5:19: warning: use of old-style cast to 'struct foo*' [-Wold-style-cast] + foo *f = (foo *)ptr; + ^~~ + ---------- + static_cast<foo *> (ptr) +</pre> + + </li> + <li>When reporting on problems within <code>extern "C"</code> linkage + specifications, the C++ compiler will now display the location of the + start of the <code>extern "C"</code>. +<pre class="blackbg"> +$ gcc -c extern-c.cc +extern-c.cc:3:1: error: template with C linkage + template <typename T> void test (void); + ^~~~~~~~ +In file included from extern-c.cc:1: +unclosed.h:1:1: note: 'extern "C"' linkage started here + extern "C" { + ^~~~~~~~~~ +extern-c.cc:3:39: error: expected '}' at end of input + template <typename T> void test (void); + ^ +In file included from extern-c.cc:1: +unclosed.h:1:12: note: to match this '{' + extern "C" { + ^ +</pre> + + </li> + <li>When reporting on mismatching template types, the C++ compiler will + now use color to highlight the mismatching parts of the template, and will + elide the parameters that are common between two mismatching templates, + printing <code>[...]</code> instead: +<pre class="blackbg"> +$ gcc templates.cc +templates.cc: In function 'void test()': +templates.cc:9:8: error: could not convert 'vector<double>()' from 'vector<double>' to 'vector<int>' + fn_1(vector<double> ()); + ^~~~~~~~~~~~~~~~~ +templates.cc:10:8: error: could not convert 'map<int, double>()' from 'map<[...],double>' to 'map<[...],int>' + fn_2(map<int, double>()); + ^~~~~~~~~~~~~~~~~~ +</pre> + + Those <code>[...]</code> elided parameters can be seen using + <code>-fno-elide-type</code>: +<pre class="blackbg"> +$ gcc templates.cc -fno-elide-type +templates.cc: In function 'void test()': +templates.cc:9:8: error: could not convert 'vector<double>()' from 'vector<double>' to 'vector<int>' + fn_1(vector<double> ()); + ^~~~~~~~~~~~~~~~~ +templates.cc:10:8: error: could not convert 'map<int, double>()' from 'map<int,double>' to 'map<int,int>' + fn_2(map<int, double>()); + ^~~~~~~~~~~~~~~~~~ +</pre> + + The C++ compiler has also gained an option + <code>-fdiagnostics-show-template-tree</code> which visualizes such + mismatching templates in a hierarchical form: +<pre class="blackbg"> +$ gcc templates-2.cc -fdiagnostics-show-template-tree +templates-2.cc: In function 'void test()': +templates-2.cc:9:8: error: could not convert 'vector<double>()' from 'vector<double>' to 'vector<int>' + vector< + [double != int]> + fn_1(vector<double> ()); + ^~~~~~~~~~~~~~~~~ +templates-2.cc:10:8: error: could not convert 'map<map<int, vector<double> >, vector<double> >()' from 'map<map<[...],vector<double>>,vector<double>>' to 'map<map<[...],vector<float>>,vector<float>>' + map< + map< + [...], + vector< + [double != float]>>, + vector< + [double != float]>> + fn_2(map<map<int, vector<double>>, vector<double>> ()); + ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +</pre> + + which again works with <code>-fno-elide-type</code>: +<pre class="blackbg"> +$ gcc templates-2.cc -fdiagnostics-show-template-tree -fno-elide-type +templates-2.cc: In function 'void test()': +templates-2.cc:9:8: error: could not convert 'vector<double>()' from 'vector<double>' to 'vector<int>' + vector< + [double != int]> + fn_1(vector<double> ()); + ^~~~~~~~~~~~~~~~~ +templates-2.cc:10:8: error: could not convert 'map<map<int, vector<double> >, vector<double> >()' from 'map<map<int,vector<double>>,vector<double>>' to 'map<map<int,vector<float>>,vector<float>>' + map< + map< + int, + vector< + [double != float]>>, + vector< + [double != float]>> + fn_2(map<map<int, vector<double>>, vector<double>> ()); + ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +</pre> + + </li> </ul> <h3 id="fortran">Fortran</h3> @@ -270,6 +502,19 @@ a work-in-progress.</h2>  <h2 id="jit">libgccjit</h2> +The libgccjit API gained four new entry points: +<ul> + <li><a href="https://gcc.gnu.org/onlinedocs/jit/topics/types.html#gcc_jit_type_get_vector">gcc_jit_type_get_vector</a> + and + </li> + <li><a href="https://gcc.gnu.org/onlinedocs/jit/topics/expressions.html#gcc_jit_context_new_rvalue_from_vector">gcc_jit_context_new_rvalue_from_vector</a> for working with vectors, + </li> + <li><a href="https://gcc.gnu.org/onlinedocs/jit/topics/types.html#gcc_jit_type_get_aligned">gcc_jit_type_get_aligned</a></li> + <li><a href="https://gcc.gnu.org/onlinedocs/jit/topics/function-pointers.html#gcc_jit_function_get_address">gcc_jit_function_get_address</a></li> +</ul> +The C code generated by +<a href="https://gcc.gnu.org/onlinedocs/jit/topics/contexts.html#gcc_jit_context_dump_reproducer_to_file">gcc_jit_context_dump_reproducer_to_file</a> +is now easier-to-read.  <h2 id="targets">New Targets and Target Specific Improvements</h2> @@ -637,6 +882,22 @@ a work-in-progress.</h2>  +<h2 id="plugins">Improvements for plugin authors</h2> +<ul> + <li>Plugins can now register a callback hook for when comments are + encountered by the C and C++ compilers, e.g. allowing for plugins + to handle documentation markup in code comments. + </li> + <li>The gdbinit support script for debugging GCC now has a + <code>break-on-diagnostic</code> command, providing an easy way + to trigger a breakpoint whenever a diagnostic is emitted. + </li> + <li>The API for creating fix-it hints now supports newlines, and for + emitting mutually incompatible fix-it hints for one diagnostic. + </li> +</ul> + + <h2>Other significant improvements</h2> <ul> <li></li> diff --git a/htdocs/gcc.css b/htdocs/gcc.css index 35321f1..718dd80 100644 --- a/htdocs/gcc.css +++ b/htdocs/gcc.css @@ -68,12 +68,17 @@ div.copyright { } div.copyright p:nth-child(3) { margin-bottom: 0; } +.bold { font-weight:bold; } .boldcyan { font-weight:bold; color:cyan; } .boldlime { font-weight:bold; color:lime; } .boldmagenta { font-weight:bold; color:magenta; } .boldred { font-weight:bold; color:red; } +.boldgreen { font-weight:bold; color:green; } .boldblue { font-weight:bold; color:blue; } +.red { color:red; } .green { color:green; } +.blue { color:blue; } +.blackbg { color:white; background-color: #000000; } /* Quote an e-mail. The first <div> has the sender, the second the quote. */ blockquote.mail div:nth-child(2) { border-left: solid blue; padding-left: 4pt; }

[committed,2/2] wwwdocs: Document my gcc 8 changes for the website (v2)

Commit Message

Comments

Patch