From patchwork Mon Apr 2 15:23:52 2018
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Gerald Pfeifer
X-Patchwork-Id: 894294
Return-Path:
X-Original-To: incoming@patchwork.ozlabs.org
Delivered-To: patchwork-incoming@bilbo.ozlabs.org
Authentication-Results: ozlabs.org;
spf=pass (mailfrom) smtp.mailfrom=gcc.gnu.org
(client-ip=209.132.180.131; helo=sourceware.org;
envelope-from=gcc-patches-return-475703-incoming=patchwork.ozlabs.org@gcc.gnu.org;
receiver=)
Authentication-Results: ozlabs.org;
dmarc=none (p=none dis=none) header.from=pfeifer.com
Authentication-Results: ozlabs.org; dkim=pass (1024-bit key;
unprotected) header.d=gcc.gnu.org header.i=@gcc.gnu.org
header.b="aWh4oa2v"; dkim-atps=neutral
Received: from sourceware.org (server1.sourceware.org [209.132.180.131])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
bits)) (No client certificate requested)
by ozlabs.org (Postfix) with ESMTPS id 40FGGg5qSnz9s28
for ;
Tue, 3 Apr 2018 01:24:10 +1000 (AEST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gcc.gnu.org; h=list-id
:list-unsubscribe:list-archive:list-post:list-help:sender:date
:from:to:subject:message-id:mime-version:content-type; q=dns; s=
default; b=jRhNxOHcryySYZJVZ63YwLshkSTPIsTi9yZVgpLm24V2Ns4iEpIT1
ohr2DpIUQCwoWrju5xoVFzUbclnfqJrJpgo4/t6Rtkhng+AwGV7H0X8Ot984lSul
D0+cXUoWWalGZi8InY9yw8G/h9nn4cKQ2G77rnkJ1KlD++0xGZDAvQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gcc.gnu.org; h=list-id
:list-unsubscribe:list-archive:list-post:list-help:sender:date
:from:to:subject:message-id:mime-version:content-type; s=
default; bh=dzBti4E1UA32EqrYViYwkhMaotc=; b=aWh4oa2vI4QHThoq5VfH
qGi1Wze4FHmXh+yAXPn+uMaELCxFD4ihhqwJ718QJTah+1rI1Mz10Ku+NmlRTx8T
+MZL05iUR5DnYvRo3TeNVsO5t1B2LyL5GodtLjr4YdRO0AZQQESF5koZR0twX6b/
In11vSfa1GtLWj94WL9bKd8=
Received: (qmail 124020 invoked by alias); 2 Apr 2018 15:24:01 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id:
List-Unsubscribe:
List-Archive:
List-Post:
List-Help:
Sender: gcc-patches-owner@gcc.gnu.org
Delivered-To: mailing list gcc-patches@gcc.gnu.org
Received: (qmail 123985 invoked by uid 89); 2 Apr 2018 15:24:01 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-11.1 required=5.0 tests=BAYES_00, GIT_PATCH_2,
GIT_PATCH_3, KAM_ASCII_DIVIDERS, KAM_SHORT, RCVD_IN_DNSWL_NONE,
SPF_PASS autolearn=ham version=3.3.2 spammy=January, fastest,
3.4, 2014
X-HELO: ainaz.pair.com
Received: from ainaz.pair.com (HELO ainaz.pair.com) (209.68.2.66) by
sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP;
Mon, 02 Apr 2018 15:23:58 +0000
Received: from ainaz.pair.com (localhost [127.0.0.1]) by ainaz.pair.com
(Postfix) with ESMTP id 616503F46A for ;
Mon, 2 Apr 2018 11:23:56 -0400 (EDT)
Received: from anthias (vie-188-118-240-174.dsl.sil.at
[188.118.240.174]) (using TLSv1.2 with cipher
ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client
certificate requested) by ainaz.pair.com (Postfix) with
ESMTPSA id 75E043F426 for ;
Mon, 2 Apr 2018 11:23:55 -0400 (EDT)
Date: Mon, 2 Apr 2018 17:23:52 +0200 (CEST)
From: Gerald Pfeifer
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Consistently spell the noun "front end"
Message-ID:
MIME-Version: 1.0
X-IsSubscribed: yes
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 @@
GNU Modula-2 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.
Modula-3 (for links see [2017-02-02]
Support for the RISC-V ISA was added, contributed by Palmer Dabbelt and Andrew Waterman.
-BRIG/HSAIL (Heterogeneous Systems Architecture Intermediate Language) frontend added
+BRIG/HSAIL (Heterogeneous Systems Architecture Intermediate Language) front end added
[2017-02-01]
Heterogeneous Systems
Architecture 1.0 BRIG (HSAIL)
- frontend was added to GCC,
+ front end was added to GCC,
enabling HSAIL finalization for gcc-supported
targets. The code was developed by
Parmance 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 @@
December 2, 2010
GCC 4.6 will support
the Go programming language. The
- new frontend was contributed by Ian Lance Taylor at Google.
+ new front end was contributed by Ian Lance Taylor at Google.
November 16, 2010
GCC 4.6 will include the
@@ -655,7 +655,7 @@
Broadband Engine Architecture (BEA).
January 1, 2007
-2006 has been a very productive year for the new Fortran frontend,
+2006 has been a very productive year for the new Fortran front end,
with lots
of improvements and fixes.
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.
gccgo
- This branch is for the Go frontend to gcc. For more information
+ This branch is for the Go front end to gcc. For more information
about the Go programming language,
see https://golang.org. 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 @@
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 -fpermissive
is used.
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 @@
GCC 3.4.6. The series is now closed.
GCC 3.4 has many improvements in the C++
-frontend. Before reporting a bug, please make sure it's really GCC,
+front end. Before reporting a bug, please make sure it's really GCC,
and not your code, that is broken.
Caveats
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 @@
- When compiling without optimizations (
-O0
), the C++
- frontend is much faster than in any previous
+ front end is much 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 @@
- Many bugs have been fixed, tools and documentation improved.
- To compile Ada from the sources, install an older working Ada compiler
and then use
--enable-languages=ada
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 Installing GCC
for details.
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 { }
instead.
-
- The C++ frontend now also produces strict aliasing warnings when
+ The C++ front end now also produces strict aliasing warnings when
-fstrict-aliasing -Wstrict-aliasing
is in effect.
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).
-The Go frontend in the 4.7.1 release fully supports
+
The Go front end in the 4.7.1 release fully supports
the Go 1 language
standard.
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.
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
here.
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 @@
Java (GCJ)
-The GCC Java frontend and associated libjava runtime library have been
+
The GCC Java front end and associated libjava runtime library have been
removed from GCC.
@@ -1246,7 +1246,7 @@
- GCC now has an internal unit-testing API and a suite of tests
for programmatic self-testing of subsystems.
- - GCC's C frontend has been extended so that it can parse dumps of
+
- 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 @@
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 (Inliner),
-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.
@@ -66,7 +66,7 @@
Move AST optimizers into the common middle end
Although C and C++ both have function at a time mode, the AST new
-inliner is only in the C++ frontend.
+inliner is only in the C++ front end.
Provable optimizer performance
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 @@
- Eliminate support for compiling with traditional C compilers in
-the language frontend subdirectories.
+the language front end subdirectories.
See: this
announcement 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 @@
Theory
-The current loop optimizer uses information passed by frontend
+
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 @@
-The objective of the project was to create a new GCC frontend able
+
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.
-This frontend, called gcccil, would allow us to
+
This front end, called gcccil, would allow us to
achieve two goals:
- The new frontend would provide a validation of a complete
+
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.
- The frontend would provide a way of producing native
+
The front end would provide a way of producing native
executables from CIL images.
@@ -413,7 +413,7 @@
Gcccil does not implement its own CLR metadata parser.
Instead, it uses Mono
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.