diff options
author | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2001-06-25 00:21:28 +0000 |
---|---|---|
committer | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2001-06-25 00:21:28 +0000 |
commit | 3774436776ab12fdb9d50b86baa70635fe88994e (patch) | |
tree | 87302f8ef83fe627cf925b4fdcb6e70da26c9e76 /gcc/doc/rtl.texi | |
parent | f36eeacd8f8d99e2636e94657dfcc32b71c7691e (diff) | |
download | gcc-3774436776ab12fdb9d50b86baa70635fe88994e.tar.gz |
* doc/c-tree.texi, doc/contrib.texi, doc/extend.texi,
doc/gcc.texi, doc/gcov.texi, doc/install.texi, doc/invoke.texi,
doc/md.texi, doc/rtl.texi, doc/tm.texi: Be more consistent about
the use of "GCC" and related terms.
* doc/gcc.1, doc/gcov.1: Regenerate.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@43547 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc/rtl.texi')
-rw-r--r-- | gcc/doc/rtl.texi | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi index 9254d27b256..50324fc9bf3 100644 --- a/gcc/doc/rtl.texi +++ b/gcc/doc/rtl.texi @@ -546,7 +546,7 @@ field and printed as @samp{/s}. @item CONSTANT_POOL_ADDRESS_P (@var{x}) Nonzero in a @code{symbol_ref} if it refers to part of the current function's ``constants pool''. These are addresses close to the -beginning of the function, and GNU CC assumes they can be addressed +beginning of the function, and GCC assumes they can be addressed directly (perhaps with the help of base registers). Stored in the @code{unchanging} field and printed as @samp{/u}. @@ -977,7 +977,7 @@ Similarly, there is only one object for the integer whose value is @item (const_double:@var{m} @var{addr} @var{i0} @var{i1} @dots{}) Represents either a floating-point constant of mode @var{m} or an integer constant too large to fit into @code{HOST_BITS_PER_WIDE_INT} -bits but small enough to fit within twice that number of bits (GNU CC +bits but small enough to fit within twice that number of bits (GCC does not provide a mechanism to represent even larger constants). In the latter case, @var{m} will be @code{VOIDmode}. @@ -2093,7 +2093,7 @@ insn. However, the reload phase may allocate a register used for one of the inputs unless the @samp{&} constraint is specified for the selected alternative (@pxref{Modifiers}). You can clobber either a specific hard register, a pseudo register, or a @code{scratch} expression; in the -latter two cases, GNU CC will allocate a hard register that is available +latter two cases, GCC will allocate a hard register that is available there for use as a temporary. For instructions that require a temporary register, you should use @@ -3189,14 +3189,14 @@ problem since reading RTL occurs only as part of building the compiler. People frequently have the idea of using RTL stored as text in a file as -an interface between a language front end and the bulk of GNU CC. This +an interface between a language front end and the bulk of GCC. This idea is not feasible. -GNU CC was designed to use RTL internally only. Correct RTL for a given +GCC was designed to use RTL internally only. Correct RTL for a given program is very dependent on the particular target machine. And the RTL does not contain all the information about the program. -The proper way to interface GNU CC to a new language front end is with +The proper way to interface GCC to a new language front end is with the ``tree'' data structure, described in the files @file{tree.h} and @file{tree.def}. The documentation for this structure (@pxref{Trees}) is incomplete. |