| Message ID | alpine.LNX.2.00.1312022242560.2185@tuna.site |
|---|---|
| State | New |
| Headers | show |
Gerald Pfeifer wrote: > Okay, so I applied this patch plus the one below to adjust > gcc-4.9/changes.html accordingly. (The first anchor there > is not stable, but for other reasons.) But it should be sufficient to check them before the release and then one is fine as the links should refer to the released versions per item13 of http://gcc.gnu.org/releasing.html (that's why I proposed to add that item). Talking about links like http://gcc.gnu.org/onlinedocs/gcc/Language-Independent-Options.html#index-fdiagnostics-color-246 What I always disliked that it doesn't linke to the @item "|-fdiagnostics-color[=WHEN]" but to the first paragraph after the @item. That makes somewhat sense if one looks at the source code: @item -fdiagnostics-color[=@var{WHEN}] @itemx -fno-diagnostics-color @opindex fdiagnostics-color @cindex highlight, color, colour @vindex GCC_COLORS @r{environment variable} Use color ... Actually, it also makes sense if one reads the texi doc, http://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#Index-Entries : "||Index entries should precede the visible material that is being indexed. [...] ||Among other reasons, that way following indexing links (in whatever context) ends up before the material, where readers want to be, instead of after." Thus, it seems as we should go through all of GCC's *texi files and swap the order of @item and @*index. Tobias |
Index: gcc-4.9/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v retrieving revision 1.43 diff -u -3 -p -r1.43 changes.html --- gcc-4.9/changes.html 30 Nov 2013 16:36:59 -0000 1.43 +++ gcc-4.9/changes.html 2 Dec 2013 21:42:24 -0000 @@ -110,7 +110,7 @@ <ul> <li>Support for colorizing diagnostics emitted by GCC has been added. The <code><a - href="http://gcc.gnu.org/onlinedocs/gcc/Language-Independent-Options.html#index-fdiagnostics_002dcolor-239" + href="http://gcc.gnu.org/onlinedocs/gcc/Language-Independent-Options.html#index-fdiagnostics-color-246" >-fdiagnostics-color=auto</a></code> will enable it when outputting to terminals, <code>-fdiagnostics-color=always</code> unconditionally. The <code>GCC_COLORS</code> environment variable @@ -136,7 +136,7 @@ </pre></li> <li>With the new <a - href="http://gcc.gnu.org/onlinedocs/gcc/Loop_002dSpecific-Pragmas.html" + href="http://gcc.gnu.org/onlinedocs/gcc/Loop-Specific-Pragmas.html" ><code>#pragma GCC ivdep</code></a>, the user can assert that there are no loop-carried dependencies which would prevent concurrent execution of consecutive iterations using SIMD (single instruction multiple data)
On Mon, 2 Dec 2013, Tobias Burnus wrote: > Looks good to me. (I fully concur that the _002d is ugly.) Okay, so I applied this patch plus the one below to adjust gcc-4.9/changes.html accordingly. (The first anchor there is not stable, but for other reasons.) Thanks for pushing for this fix! Gerald