diff options
Diffstat (limited to 'contrib/gcc/doc/portability.texi')
| -rw-r--r-- | contrib/gcc/doc/portability.texi | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/contrib/gcc/doc/portability.texi b/contrib/gcc/doc/portability.texi index b05698d..e65e979 100644 --- a/contrib/gcc/doc/portability.texi +++ b/contrib/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. |
