[PATCH] Fix documentation typos.

Gerald Pfeifer pfeifer@dbai.tuwien.ac.at
Tue Feb 19 10:04:00 GMT 2002


On Tue, 19 Feb 2002, Gaute B Strokkenes wrote:
> This is a resend of:
>
>   http://gcc.gnu.org/ml/gcc-patches/2002-01/msg00354.html
>   http://gcc.gnu.org/ml/gcc-patches/2002-01/msg00495.html
>   http://gcc.gnu.org/ml/gcc-patches/2002-01/msg02058.html
>
> It would be nice if anyone could have a look at this simple, 4-byte
> change sometime soon.

It's really embarrassing that nobody has reviewed/committed this yet,
but perhaps it's because you haven't provided a ChangeLog entry?

I created a ChangeLog entry and committed the rtl.texi patch with
a bit of reformatting to avoid overly long lines. Can someone else
please review the other part of the patch?!

Thanks for the patch (and your patience),
Gerald


2002-02-19  Gaute B Strokkenes <gs234@cam.ac.uk>

        * doc/rtl.texi (Flags, MEM_SCALAR_P): Fix typo.

Index: doc/rtl.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/rtl.texi,v
retrieving revision 1.28
diff -u -3 -p -r1.28 rtl.texi
--- rtl.texi	2002/02/19 05:01:24	1.28
+++ rtl.texi	2002/02/19 17:17:52
@@ -501,9 +501,9 @@ Stored in the @code{jump} field and prin
 In @code{mem} expressions, nonzero for reference to a scalar known not
 to be a member of a structure, union, or array.  Zero for such
 references and for indirections through pointers, even pointers pointing
-to scalar types.  If both this flag and @code{MEM_STRUCT_P} are clear, then we
-don't know whether this @code{mem} is in a structure or not.  Both flags should
-never be simultaneously set.
+to scalar types.  If both this flag and @code{MEM_IN_STRUCT_P} are clear,
+then we don't know whether this @code{mem} is in a structure or not.
+Both flags should never be simultaneously set.
 Stored in the @code{frame_related} field and printed as @samp{/f}.

 @findex MEM_VOLATILE_P




More information about the Gcc-patches mailing list