This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [doc, PATCH] Remove duplicated "@subsubsection Statements"


2010/12/19 Mingjie Xing <mingjie.xing@gmail.com>:
> 2010/12/19 Mingjie Xing <mingjie.xing@gmail.com>:
>> Hi,
>>
>> There is a duplicated "@subsubsection Statements" in generic.texi,
>> which seems a ?mistake. ?This patch simply remove the inappropriate
>> part.
>>
>> Is it OK?
>>
>> Thanks,
>> Mingjie
>>
>> 2010-12-19 ?Mingjie Xing ?<mingjie.xing@gmail.com>
>>
>> ? ? ? ?* doc/generic.texi: Remove duplicated "@subsubsection Statements".
>>
>>
>
> I find there are two places in doc/*.texi, that appears "see @pxref".
> So I updated the patch to also remove the word "see" before "@pxref".
>
> 010-12-19 ?Mingjie Xing ?<mingjie.xing@gmail.com>
>
> ? ? ? ?* doc/generic.texi: Remove duplicated "@subsubsection Statements".
> ? ? ? ?Remove the word "see" before "@pxref".
> ? ? ? ?* doc/rtl.texi: Remove the word "see" before "@pxref".
>
> Index: doc/generic.texi
> ===================================================================
> --- doc/generic.texi ? ?(revision 168044)
> +++ doc/generic.texi ? ?(working copy)
> @@ -2420,14 +2420,6 @@ optimization options specified on the co
>
> ?@end ftable
>
> -@subsubsection Statements
> -
> -There are tree nodes corresponding to all of the source-level
> -statement constructs, used within the C and C++ frontends. ?These are
> -enumerated here, together with a list of the various macros that can
> -be used to obtain information about them. ?There are a few macros that
> -can be used with all statements:
> -
> ?@c ---------------------------------------------------------------------
> ?@c Language-dependent trees
> ?@c ---------------------------------------------------------------------
> @@ -2637,7 +2629,7 @@ type. ?In that case, the @code{TYPE_PTRM
> ?@code{POINTER_TYPE} pointing to a @code{METHOD_TYPE}. ?The
> ?@code{METHOD_TYPE} is the type of a function pointed to by the
> ?pointer-to-member function. ?If @code{TYPE_PTRMEMFUNC_P} does not hold,
> -this type is a class type. ?For more information, see @pxref{Classes}.
> +this type is a class type. ?For more information, @pxref{Classes}.
>
> ?@item UNKNOWN_TYPE
> ?This node is used to represent a type the knowledge of which is
> Index: doc/rtl.texi
> ===================================================================
> --- doc/rtl.texi ? ? ? ?(revision 168044)
> +++ doc/rtl.texi ? ? ? ?(working copy)
> @@ -1271,7 +1271,7 @@ accumulator. ?The default format is ``64
> ?is a machine-specific set of bits used to represent the result of a
> ?comparison operation. ?Other machine-specific modes may also be used for
> ?the condition code. ?These modes are not used on machines that use
> -@code{cc0} (see @pxref{Condition Code}).
> +@code{cc0} (@pxref{Condition Code}).
>
> ?@findex BLKmode
> ?@item BLKmode
>

Ping


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]