I noticed this on one recent page, and looking into it then ended up fixing a dozen more, historical and current.
Committed. Gerald Index: htdocs/frontends.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/frontends.html,v retrieving revision 1.40 diff -u -r1.40 frontends.html --- htdocs/frontends.html 28 Dec 2016 00:55:24 -0000 1.40 +++ htdocs/frontends.html 2 Apr 2018 15:16:30 -0000 @@ -40,8 +40,8 @@ <li><a href="http://www.nongnu.org/gm2/";>GNU Modula-2</a> implements the PIM2, PIM3, PIM4 and ISO dialects of the language. The compiler is fully operational with the GCC 4.1.2 back end (on GNU/Linux x86 -systems). Work is in progress to move the frontend to the GCC trunk. -The frontend is mostly written in Modula-2, but includes a bootstrap +systems). Work is in progress to move the front end to the GCC trunk. +The front end is mostly written in Modula-2, but includes a bootstrap procedure via a heavily modified version of p2c.</li> <li>Modula-3 (for links see <a Index: htdocs/index.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v retrieving revision 1.1079 diff -u -r1.1079 index.html --- htdocs/index.html 27 Mar 2018 13:34:41 -0000 1.1079 +++ htdocs/index.html 2 Apr 2018 15:16:30 -0000 @@ -82,11 +82,11 @@ <span class="date">[2017-02-02]</span></dt> <dd>Support for the <a href="https://riscv.org";>RISC-V ISA</a> was added, contributed by Palmer Dabbelt and Andrew Waterman.</dd> -<dt><span>BRIG/HSAIL (Heterogeneous Systems Architecture Intermediate Language) frontend added</span> +<dt><span>BRIG/HSAIL (Heterogeneous Systems Architecture Intermediate Language) front end added</span> <span class="date">[2017-02-01]</span></dt> <dd><a href="http://www.hsafoundation.com/";> Heterogeneous Systems Architecture 1.0</a> BRIG (HSAIL) - <a href="gcc-7/changes.html#brig">frontend was added to GCC</a>, + <a href="gcc-7/changes.html#brig">front end was added to GCC</a>, enabling HSAIL finalization for gcc-supported targets. The code was developed by <a href="http://parmance.com";>Parmance</a> with sponsorship from Index: htdocs/news.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/news.html,v retrieving revision 1.159 diff -u -r1.159 news.html --- htdocs/news.html 18 Nov 2017 01:08:36 -0000 1.159 +++ htdocs/news.html 2 Apr 2018 15:16:31 -0000 @@ -417,7 +417,7 @@ <dt>December 2, 2010</dt> <dd><a href="gcc-4.6/changes.html#go">GCC 4.6</a> will support the <a href="https://golang.org/";>Go programming language</a>. The - new frontend was contributed by Ian Lance Taylor at Google.</dd> + new front end was contributed by Ian Lance Taylor at Google.</dd> <dt>November 16, 2010</dt> <dd><a href="gcc-4.6/changes.html#libquadmath">GCC 4.6</a> will include the @@ -655,7 +655,7 @@ Broadband Engine Architecture (BEA).</dd> <dt>January 1, 2007</dt> -<dd>2006 has been a very productive year for the new Fortran frontend, +<dd>2006 has been a very productive year for the new Fortran front end, with <a href="https://gcc.gnu.org/ml/gcc/2007-01/msg00059.html";>lots of improvements and fixes</a>.</dd> Index: htdocs/svn.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/svn.html,v retrieving revision 1.218 diff -u -r1.218 svn.html --- htdocs/svn.html 27 Jul 2017 09:17:28 -0000 1.218 +++ htdocs/svn.html 2 Apr 2018 15:16:32 -0000 @@ -547,7 +547,7 @@ be marked with the tag [4_4-plugins] in the Subject line.</dd> <dt>gccgo</dt> - <dd>This branch is for the Go frontend to gcc. For more information + <dd>This branch is for the Go front end to gcc. For more information about the Go programming language, see <a href="https://golang.org/";>https://golang.org</a>. The branch is maintained by Ian Lance Taylor. Patches should be Index: htdocs/bugs/index.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/index.html,v retrieving revision 1.121 diff -u -r1.121 index.html --- htdocs/bugs/index.html 1 Dec 2017 01:18:03 -0000 1.121 +++ htdocs/bugs/index.html 2 Apr 2018 15:16:32 -0000 @@ -684,7 +684,7 @@ <p>Non-conforming legacy code that worked with older versions of GCC may be rejected by more recent compilers. There is no command-line switch to ensure compatibility in general, because trying to parse standard-conforming and -old-style code at the same time would render the C++ frontend unmaintainable. +old-style code at the same time would render the C++ front end unmaintainable. However, some non-conforming constructs are allowed when the command-line option <code>-fpermissive</code> is used.</p> Index: htdocs/egcs-1.1/c++features.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/egcs-1.1/c++features.html,v retrieving revision 1.5 diff -u -r1.5 c++features.html --- htdocs/egcs-1.1/c++features.html 11 Feb 2002 09:47:47 -0000 1.5 +++ htdocs/egcs-1.1/c++features.html 2 Apr 2018 15:16:33 -0000 @@ -31,7 +31,7 @@ * protected virtual inheritance is now supported. * Loops are optimized better; we now move the test to the end in most - cases, like the C frontend does. + cases, like the C front end does. * For class D derived from B which has a member 'int i', &D::i is now of type 'int B::*' instead of 'int D::*'. Index: htdocs/gcc-2.95/c++features.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-2.95/c++features.html,v retrieving revision 1.7 diff -u -r1.7 c++features.html --- htdocs/gcc-2.95/c++features.html 23 Jan 2002 15:42:26 -0000 1.7 +++ htdocs/gcc-2.95/c++features.html 2 Apr 2018 15:16:33 -0000 @@ -66,7 +66,7 @@ * protected virtual inheritance is now supported. * Loops are optimized better; we now move the test to the end in most - cases, like the C frontend does. + cases, like the C front end does. * For class D derived from B which has a member 'int i', &D::i is now of type 'int B::*' instead of 'int D::*'. Index: htdocs/gcc-3.4/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.4/changes.html,v retrieving revision 1.163 diff -u -r1.163 changes.html --- htdocs/gcc-3.4/changes.html 30 Dec 2016 14:48:58 -0000 1.163 +++ htdocs/gcc-3.4/changes.html 2 Apr 2018 15:16:34 -0000 @@ -15,7 +15,7 @@ <a href="#3.4.6">GCC 3.4.6</a>. The series is now closed.</p> <p><em>GCC 3.4 has <a href="#cplusplus">many improvements in the C++ -frontend</a>. Before reporting a bug, please make sure it's really GCC, +front end</a>. Before reporting a bug, please make sure it's really GCC, and not your code, that is broken.</em></p> <h2>Caveats</h2> Index: htdocs/gcc-4.0/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.0/changes.html,v retrieving revision 1.70 diff -u -r1.70 changes.html --- htdocs/gcc-4.0/changes.html 29 Mar 2017 16:26:00 -0000 1.70 +++ htdocs/gcc-4.0/changes.html 2 Apr 2018 15:16:34 -0000 @@ -150,7 +150,7 @@ <ul> <li>When compiling without optimizations (<code>-O0</code>), the C++ - frontend is <em>much</em> faster than in any previous + front end is <em>much</em> faster than in any previous versions of GCC. Independent testers have measured speed-ups up to 25% in real-world production code, compared to the 3.4 family (which was already the fastest version to date). Upgrading from older @@ -367,7 +367,7 @@ <li>Many bugs have been fixed, tools and documentation improved.</li> <li>To compile Ada from the sources, install an older working Ada compiler and then use <code>--enable-languages=ada</code> at configuration time, - since the Ada frontend is not currently activated by default. See + since the Ada front end is not currently activated by default. See the <a href="https://gcc.gnu.org/install/";>Installing GCC</a> for details. </li> Index: htdocs/gcc-4.2/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.2/changes.html,v retrieving revision 1.42 diff -u -r1.42 changes.html --- htdocs/gcc-4.2/changes.html 7 Feb 2017 23:06:23 -0000 1.42 +++ htdocs/gcc-4.2/changes.html 2 Apr 2018 15:16:35 -0000 @@ -183,7 +183,7 @@ To suppress the warning in valid cases, use <code>{ }</code> instead. </li> <li> - The C++ frontend now also produces strict aliasing warnings when + The C++ front end now also produces strict aliasing warnings when <code>-fstrict-aliasing -Wstrict-aliasing</code> is in effect. </li> </ul> Index: htdocs/gcc-4.7/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v retrieving revision 1.146 diff -u -r1.146 changes.html --- htdocs/gcc-4.7/changes.html 3 Mar 2017 10:07:32 -0000 1.146 +++ htdocs/gcc-4.7/changes.html 2 Apr 2018 15:16:35 -0000 @@ -1015,7 +1015,7 @@ complete (that is, it is possible that some PRs that have been fixed are not listed here).</p> -<p>The Go frontend in the 4.7.1 release fully supports +<p>The Go front end in the 4.7.1 release fully supports the <a href="https://golang.org/doc/go1";>Go 1 language standard.</a></p> Index: htdocs/gcc-5/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v retrieving revision 1.148 diff -u -r1.148 changes.html --- htdocs/gcc-5/changes.html 10 Oct 2017 08:18:28 -0000 1.148 +++ htdocs/gcc-5/changes.html 2 Apr 2018 15:16:36 -0000 @@ -619,7 +619,7 @@ functions from bytecode to machine code</a>.</p> <p>The library can also be used for ahead-of-time compilation, enabling -GCC to be plugged into a pre-existing frontend. An example of using +GCC to be plugged into a pre-existing front end. An example of using this to build a compiler for an esoteric language we'll refer to as "brainf" can be seen <a href="https://gcc.gnu.org/onlinedocs/gcc-5.1.0/jit/intro/tutorial05.html";> here</a>.</p> Index: htdocs/gcc-7/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/changes.html,v retrieving revision 1.100 diff -u -r1.100 changes.html --- htdocs/gcc-7/changes.html 1 Apr 2018 22:56:06 -0000 1.100 +++ htdocs/gcc-7/changes.html 2 Apr 2018 15:16:37 -0000 @@ -808,7 +808,7 @@ <h3 id="java">Java (GCJ)</h3> -<p>The GCC Java frontend and associated libjava runtime library have been +<p>The GCC Java front end and associated libjava runtime library have been removed from GCC.</p> <!-- .................................................................. --> @@ -1246,7 +1246,7 @@ <ul> <li>GCC now has an internal unit-testing API and a suite of tests for programmatic self-testing of subsystems.</li> - <li>GCC's C frontend has been extended so that it can parse dumps of + <li>GCC's C front end has been extended so that it can parse dumps of GCC's internal representations, allowing for DejaGnu tests that more directly exercise specific optimization passes. This covers both the Index: htdocs/projects/ast-optimizer.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/projects/ast-optimizer.html,v retrieving revision 1.8 diff -u -r1.8 ast-optimizer.html --- htdocs/projects/ast-optimizer.html 27 Jun 2014 15:04:40 -0000 1.8 +++ htdocs/projects/ast-optimizer.html 2 Apr 2018 15:16:37 -0000 @@ -27,7 +27,7 @@ <p>Historically, GCC generated RTL one statement at a time, so the AST did not stay around very long. This has changed with 'function at a time' compilation (<a href="../news/inlining.html">Inliner</a>), -which both C and C++ frontends now implement. With the AST for complete +which both C and C++ front ends now implement. With the AST for complete functions, and the additional semantic information they contain, the opportunity for new optimizations presents itself.</p> @@ -66,7 +66,7 @@ <h3>Move AST optimizers into the common middle end</h3> <p>Although C and C++ both have function at a time mode, the AST new -inliner is only in the C++ frontend.</p> +inliner is only in the C++ front end.</p> <h3>Provable optimizer performance</h3> Index: htdocs/projects/beginner.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/projects/beginner.html,v retrieving revision 1.65 diff -u -r1.65 beginner.html --- htdocs/projects/beginner.html 3 Feb 2017 08:16:13 -0000 1.65 +++ htdocs/projects/beginner.html 2 Apr 2018 15:16:37 -0000 @@ -127,7 +127,7 @@ </li> <li>Eliminate support for compiling with traditional C compilers in -the language frontend subdirectories. +the language front end subdirectories. <p>See: <a href="https://gcc.gnu.org/ml/gcc/2002-06/msg00871.html";>this announcement</a> and the discussion following it which clarifies the Index: htdocs/projects/cfg.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cfg.html,v retrieving revision 1.23 diff -u -r1.23 cfg.html --- htdocs/projects/cfg.html 11 Mar 2017 23:40:55 -0000 1.23 +++ htdocs/projects/cfg.html 2 Apr 2018 15:16:37 -0000 @@ -78,7 +78,7 @@ <h4>Theory</h4> -<p>The current loop optimizer uses information passed by frontend +<p>The current loop optimizer uses information passed by the front end to discover loop constructs to simplify flow analysis. It is difficult to keep the information up-to-date and nowday it is easy to implement the loop discovery code on CFG. Index: htdocs/projects/cli.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cli.html,v retrieving revision 1.29 diff -u -r1.29 cli.html --- htdocs/projects/cli.html 27 Jan 2017 21:09:05 -0000 1.29 +++ htdocs/projects/cli.html 2 Apr 2018 15:16:37 -0000 @@ -342,14 +342,14 @@ <h2><a name="frontend">The CLI front end</a></h2> -<p>The objective of the project was to create a new GCC frontend able +<p>The objective of the project was to create a new GCC front end able to take a .NET executable as input, and produce optimized native code as output.</p> -<p>This frontend, called <i>gcccil</i>, would allow us to +<p>This front end, called <i>gcccil</i>, would allow us to achieve two goals:</p> <ul> - <li><p>The new frontend would provide a validation of a complete + <li><p>The new front end would provide a validation of a complete static compilation path from C to native code using CIL as intermediate format. This would allow using CIL as a distribution format for executables. In this model, the CIL image could be @@ -357,7 +357,7 @@ customer could recompile said image for the native platform that he prefers using GCC.</p></li> - <li><p>The frontend would provide a way of producing native + <li><p>The front end would provide a way of producing native executables from CIL images.</p></li> </ul> @@ -413,7 +413,7 @@ <p><i>Gcccil</i> does not implement its own CLR metadata parser. Instead, it uses <a href="http://www.mono-project.com/";>Mono</a> to "parse" the input assembly. That is, Mono is used to load the assembly -and parse the metadata and types. The frontend only has to parse the +and parse the metadata and types. The front end only has to parse the actual CIL code of each method. Mono provides a comprehensive API to allow this.</p>
