diff options
author | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2004-07-02 23:57:12 +0000 |
---|---|---|
committer | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2004-07-02 23:57:12 +0000 |
commit | 153e79bc70f4750380851847e107ccff1f763fbe (patch) | |
tree | 958b578b1dceccdb7246fb9f76df3bb9c636e4e2 /gcc/doc/portability.texi | |
parent | f10ff0e0180ce8d4b427df5dbe7e21cd8dbfc6db (diff) | |
download | gcc-153e79bc70f4750380851847e107ccff1f763fbe.tar.gz |
* doc/bugreport.texi, doc/configterms.texi, doc/contrib.texi,
doc/contribute.texi, doc/cpp.texi, doc/cppinternals.texi,
doc/extend.texi, doc/install.texi, doc/invoke.texi, doc/md.texi,
doc/portability.texi, doc/tree-ssa.texi, doc/trouble.texi: Avoid
some first-person references and patronizing comments. Based on
printed manual.
* doc/invoke.texi: Don't reference fortran@gnu.org.
* doc/trouble.texi (Warning when a non-void function value is
ignored): Rewrite. From Russ Allbery and Chris Devers.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@84034 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc/portability.texi')
-rw-r--r-- | gcc/doc/portability.texi | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/gcc/doc/portability.texi b/gcc/doc/portability.texi index b05698dcfa6..e65e979fcca 100644 --- a/gcc/doc/portability.texi +++ b/gcc/doc/portability.texi @@ -1,5 +1,5 @@ @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, -@c 1999, 2000, 2001, 2002 Free Software Foundation, Inc. +@c 1999, 2000, 2001, 2002, 2004 Free Software Foundation, Inc. @c This is part of the GCC manual. @c For copying conditions, see the file gcc.texi. @@ -18,9 +18,9 @@ GCC gets most of the information about the target machine from a machine description which gives an algebraic formula for each of the machine's instructions. This is a very clean way to describe the target. But when the compiler needs information that is difficult to express in this -fashion, I have not hesitated to define an ad-hoc parameter to the machine -description. The purpose of portability is to reduce the total work needed -on the compiler; it was not of interest for its own sake. +fashion, ad-hoc parameters have been defined for machine descriptions. +The purpose of portability is to reduce the total work needed on the +compiler; it was not of interest for its own sake. @cindex endianness @cindex autoincrement addressing, availability @@ -31,9 +31,10 @@ significant byte has the highest or lowest address of the bytes in a word) and the availability of autoincrement addressing. In the RTL-generation pass, it is often necessary to have multiple strategies for generating code for a particular kind of syntax tree, strategies that are usable for different -combinations of parameters. Often I have not tried to address all possible -cases, but only the common ones or only the ones that I have encountered. -As a result, a new target may require additional strategies. You will know +combinations of parameters. Often, not all possible cases have been +addressed, but only the common ones or only the ones that have been +encountered. As a result, a new target may require additional +strategies. You will know if this happens because the compiler will call @code{abort}. Fortunately, the new strategies can be added in a machine-independent fashion, and will affect only the target machines that need them. |