[wwwdocs] back-end -> back end

Gerald Pfeifer gerald@pfeifer.com
Tue Dec 3 01:12:00 GMT 2013


After changing a backend to back end or back-end, I realized we had
a number of uses of back-end which actually were about the noun (back
end).

Fixed thusly.

Index: svn.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svn.html,v
retrieving revision 1.190
diff -u -3 -p -r1.190 svn.html
--- svn.html	3 Dec 2013 01:04:41 -0000	1.190
+++ svn.html	3 Dec 2013 01:08:52 -0000
@@ -377,7 +377,7 @@ the command <code>svn log --stop-on-copy
   line.</dd>
 
   <dt><a href="projects/cli.html">st/cli-be</a></dt>
-  <dd>The goal of the branch is to develop a back-end producing CLI binaries,
+  <dd>The goal of the branch is to develop a back end producing CLI binaries,
   compliant with ECMA-335 specification.
   This branch was originally maintained by Roberto Costa
   <<a href="mailto:robsettantasei@gmail.com">robsettantasei@gmail.com</a>>.
Index: gcc-3.0/criteria.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.0/criteria.html,v
retrieving revision 1.30
diff -u -3 -p -r1.30 criteria.html
--- gcc-3.0/criteria.html	29 Dec 2006 10:03:38 -0000	1.30
+++ gcc-3.0/criteria.html	3 Dec 2013 01:08:53 -0000
@@ -78,7 +78,7 @@ be completed before GCC 3.0 is released:
        like the other GCC front-ends.  This conversion will enable the
        simplification, optimization, and removal of code in the
        machine-independent portions of the compiler, as well as in 
-       the various back-ends.  <strong>Done</strong>.</p>
+       the various back ends.  <strong>Done</strong>.</p>
 </li>
 <li><p>Chill Front-End Garbage Collection</p>
     <p>Like the Java front-end, the Chill front-end will be converted
Index: gcc-3.0/features.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.0/features.html,v
retrieving revision 1.34
diff -u -3 -p -r1.34 features.html
--- gcc-3.0/features.html	31 Oct 2013 23:52:44 -0000	1.34
+++ gcc-3.0/features.html	3 Dec 2013 01:08:53 -0000
@@ -132,7 +132,7 @@
 <h2>New Targets and Target Specific Improvements</h2>
 
   <ul>
-    <li>New x86 back-end, generating much improved code.</li>
+    <li>New x86 back end, generating much improved code.</li>
     <li>Support for a generic i386-elf target contributed.</li>
     <li>New option to emit x86 assembly code using Intel style syntax
         (<code>-mintel-syntax</code>).</li>
Index: projects/cli.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cli.html,v
retrieving revision 1.23
diff -u -3 -p -r1.23 cli.html
--- projects/cli.html	3 Dec 2013 01:04:42 -0000	1.23
+++ projects/cli.html	3 Dec 2013 01:08:54 -0000
@@ -12,8 +12,8 @@
 <li><a href="#news">Latest news</a></li>
 <li><a href="#intro">Introduction</a></li>
 <li><a href="#contributing">Contributing</a></li>
-<li><a href="#internals">The CLI back-end</a></li>
-<li><a href="#frontend">The CLI front-end</a></li>
+<li><a href="#internals">The CLI back end</a></li>
+<li><a href="#frontend">The CLI front end</a></li>
 <li><a href="#readings">Readings</a></li>
 </ul>
 
@@ -59,7 +59,7 @@ that allows most of c applications to be
 
 <dl>
 <dt>2007-07-10</dt>
-<dd><p>Added CLI front-end</p></dd>
+<dd><p>Added CLI front end</p></dd>
 </dl>
 
 <dl>
@@ -93,11 +93,11 @@ with different abstraction levels, from 
 to low-level languages with no managed execution at all.
 </p>
 <p>
-The purpose of this project is to develop a GCC back-end that produces
+The purpose of this project is to develop a GCC back end that produces
 CLI-compliant binaries.
 The initial focus is on C language (more precisely, C99);
 C++ is likely to be considered in the future, as well as any
-other language for which there is an interest for a CLI back-end.
+other language for which there is an interest for a CLI back end.
 </p>
 <p>
 STMicroelectronics started this project in 2006,
@@ -106,7 +106,7 @@ as part of the European funded project <
 <p>
 In 2007 to explore the potential of .NET as a deployment file format, in
 collaboration with <a href="http://www.hipeac.net/">HiPEAC</a>, we
-developped also a CIL front-end (always using GCC).
+developped also a CIL front end (always using GCC).
 </p>
 
 <p>
@@ -151,9 +151,9 @@ gcc CLI Backend and the CLI Frontend and
 <a href="http://gcc.gnu.org/viewcvs/branches/st/README?view=markup">Build instructions</a>
 </p>
 
-<h2><a name="internals">The CLI back-end</a></h2>
+<h2><a name="internals">The CLI back end</a></h2>
 <p>
-Unlike a typical GCC back-end, CLI back-end stops the compilation flow
+Unlike a typical GCC back end, the CLI backnend stops the compilation flow
 at the end of the middle-end passes and, without going through any RTL
 pass, it emits CIL bytecode from GIMPLE representation.
 As a matter of fact, RTL is not a convenient representation to emit
@@ -171,7 +171,7 @@ data type information that is not preser
 
 <h3><a name="mmodel">Target machine model</a></h3>
 <p>
-Like existing GCC back-ends, CLI is truly seen as a target machine
+Like existing GCC back ends, CLI is truly seen as a target machine
 and, as such, it follows GCC policy about the organization of the
 back-end specific files.
 </p>
@@ -202,10 +202,10 @@ This is an overview of such a descriptio
   attribute).</li>
 
   <li>Properties exclusively needed by RTL passes are skipped.
-  This is a mere consequence of the fact that CLI back-end starts
+  This is a mere consequence of the fact that the CLI back end starts
   from GIMPLE and it does not go through RTL at all.</li>
 
-  <li>Though CLI back-end does not reach RTL passes, there is a
+  <li>Though the CLI back end does not reach RTL passes, there is a
   minimum set of RTL-related description that must be present anyway.
   For instance, a few instruction selection patterns are mandatory,
   while others are used by some heuristics for cost estimation;
@@ -267,7 +267,7 @@ two stack slots. Duplication is possible
 <p>
 To preserve the semantics of GCC built-in functions we turn into CIL built-ins
 during this phase and we provide implementations for them in the support library
-which ships with our back-end so that virtual machines which do not recognize
+which ships with our back end so that virtual machines which do not recognize
 them can still execute the code correctly. Other built-ins which can be mapped
 efficiently on CIL code are expanded in this phase. For example
 <code>__builtin_memcpy</code> is turned into a <code>cpblk</code> instruction.
@@ -342,7 +342,7 @@ pointers and optionally the basic block 
 probabilities.
 </p>
 
-<h2><a name="frontend">The CLI front-end</a></h2>
+<h2><a name="frontend">The CLI front end</a></h2>
 
 <p>The objective of the project was to create a new GCC frontend able
 to take a .NET executable as input, and produce optimized native code
@@ -366,7 +366,7 @@ achieve two goals:</p>
 </ul>
 
 <p><i>Gcccil</i> targets primarily assemblies produced by the GCC CIL
-back-end since this is more convenient for achieving the first of the
+back end since this is more convenient for achieving the first of the
 goals mentioned above.</p>
 
 <h3>Implemented functionality</h3>
@@ -375,8 +375,8 @@ goals mentioned above.</p>
 possible to produce a complete implementation of the
 standard. However, the subset implemented is enough to correctly
 compile some medium sized CIL programs produced by the GCC CIL
-back-end.  Basically, everything required to compile assemblies
-produced by GCC CIL back-end has been implemented and tested.</p>
+back end.  Basically, everything required to compile assemblies
+produced by the GCC CIL back end has been implemented and tested.</p>
 
 <p>In particular, the following features have been implemented:</p>
 <ul>
@@ -395,7 +395,7 @@ produced by GCC CIL back-end has been im
 <h3>Missing functionality</h3>
 
 <p>On the other hand, almost every feature which is not required to
-compile assemblies produced by GCC CIL back-end has not been
+compile assemblies produced by the GCC CIL back end has not been
 implemented yet.</p>
 <p> This includes:</p>
 <ul>
Index: projects/tree-profiling.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/tree-profiling.html,v
retrieving revision 1.2
diff -u -3 -p -r1.2 tree-profiling.html
--- projects/tree-profiling.html	4 Jul 2004 21:00:54 -0000	1.2
+++ projects/tree-profiling.html	3 Dec 2013 01:08:54 -0000
@@ -17,7 +17,7 @@ function inlining.  At the heart of this
 added for GCC 3.4, and the effort to maintain the control flow graph and
 profile information over expanding from GIMPLE, which is the tree-based
 intermediate representation, to RTL, the intermediate representation of
-GCC's back-ends.</p>
+GCC's back ends.</p>
 
 <p>Longer-term goals include adding support for doing some optimizations
 (such as CCP and DCE) before inlining, and implementing a framework for
Index: projects/lto/architecture.tex
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/lto/architecture.tex,v
retrieving revision 1.1
diff -u -3 -p -r1.1 architecture.tex
--- projects/lto/architecture.tex	16 Nov 2005 22:24:58 -0000	1.1
+++ projects/lto/architecture.tex	3 Dec 2013 01:08:54 -0000
@@ -32,7 +32,7 @@ optimizer. The input language for this f
 object files, not programming language source code.  The front end
 will extract the relevant data from the relocatable object files,
 build a TREE representation for the input program, and, then, use the
-same optimizers and back-ends already present in GCC.
+same optimizers and back ends already present in GCC.
 
 In order to accommodate Requirement~\ref{req:debug}, the back end will
 be modified to permit the generation of multiple symbols with the same



More information about the Gcc-patches mailing list