From: Uros Bizjak <ubizjak@gmail.com>
Date: Tue, 26 Feb 2019 17:21:43 +0000 (+0100)
Subject: extend.texi (__builtin_object_size): Use @pxref instead of @xref inside parenthesis.
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=062937663cd60daaf67599a7f8fcbed21636b111;p=gcc.git

extend.texi (__builtin_object_size): Use @pxref instead of @xref inside parenthesis.

	* doc/extend.texi (__builtin_object_size):
	Use @pxref instead of @xref inside parenthesis.
	(__builtin_has_attribute): Add missing comma after @xref.
	(__builtin_object_size): Ditto.
	* doc/md.texi (cond_*{mode}): Use @samp instead of @var around op1[i].
	* fortran/invoke.texi (-ffpe-trap): Use @var for every item
	in the list.

From-SVN: r269219
---

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 92a90bcfa69..8730434a29c 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,13 @@
+2019-02-26  Uroš Bizjak  <ubizjak@gmail.com>
+
+	* doc/extend.texi (__builtin_object_size):
+	Use @pxref instead of @xref inside parenthesis.
+	(__builtin_has_attribute): Add missing comma after @xref.
+	(__builtin_object_size): Ditto.
+	* doc/md.texi (cond_*{mode}): Use @samp instead of @var around op1[i].
+	* fortran/invoke.texi (-ffpe-trap): Use @var for every item
+	in the list.
+
 2019-02-26  Jeff Law  <law@redhat.com>
 
 	PR rtl-optimization/87761
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 696d892cfec..7425d890617 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -11775,7 +11775,7 @@ is a built-in construct that returns a constant number of bytes from
 @var{ptr} to the end of the object @var{ptr} pointer points to
 (if known at compile time).  To determine the sizes of dynamically allocated
 objects the function relies on the allocation functions called to obtain
-the storage to be declared with the @code{alloc_size} attribute (@xref{Common
+the storage to be declared with the @code{alloc_size} attribute (@pxref{Common
 Function Attributes}).  @code{__builtin_object_size} never evaluates
 its arguments for side effects.  If there are any side effects in them, it
 returns @code{(size_t) -1} for @var{type} 0 or 1 and @code{(size_t) 0}
@@ -12560,7 +12560,7 @@ restrictions as the argument to @code{typeof} (@pxref{Typeof}).  The
 @var{attribute} argument is an attribute name optionally followed by
 a comma-separated list of arguments enclosed in parentheses.  Both forms
 of attribute names---with and without double leading and trailing
-underscores---are recognized.  @xref{Attribute Syntax} for details.
+underscores---are recognized.  @xref{Attribute Syntax}, for details.
 When no attribute arguments are specified for an attribute that expects
 one or more arguments the function returns @code{true} if
 @var{type-or-expression} has been declared with the attribute regardless
@@ -13163,7 +13163,8 @@ and GCC does not issue a warning.
 @end deftypefn
 
 @deftypefn {Built-in Function}{size_t} __builtin_object_size (const void * @var{ptr}, int @var{type})
-Returns the size of an object pointed to by @var{ptr}.  @xref{Object Size Checking} for a detailed description of the function.
+Returns the size of an object pointed to by @var{ptr}.  @xref{Object Size
+Checking}, for a detailed description of the function.
 @end deftypefn
 
 @deftypefn {Built-in Function} double __builtin_huge_val (void)
diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
index 6ffb69b2059..30612a6aecb 100644
--- a/gcc/doc/md.texi
+++ b/gcc/doc/md.texi
@@ -6628,7 +6628,7 @@ for (i = 0; i < GET_MODE_NUNITS (@var{m}); i++)
 where, for example, @var{op} is @code{+} for @samp{cond_add@var{mode}}.
 
 When defined for floating-point modes, the contents of @samp{op3[i]}
-are not interpreted if @var{op1[i]} is false, just like they would not
+are not interpreted if @samp{op1[i]} is false, just like they would not
 be in a normal C @samp{?:} condition.
 
 Operands 0, 2, 3 and 4 all have mode @var{m}.  Operand 1 is a scalar
diff --git a/gcc/fortran/invoke.texi b/gcc/fortran/invoke.texi
index a5d81960a61..8364c67b2df 100644
--- a/gcc/fortran/invoke.texi
+++ b/gcc/fortran/invoke.texi
@@ -1205,7 +1205,7 @@ these three exceptions is probably a good idea.
 
 If the option is used more than once in the command line, the lists will
 be joined: '@code{ffpe-trap=}@var{list1} @code{ffpe-trap=}@var{list2}'
-is equivalent to @code{ffpe-trap=}@var{list1,list2}.
+is equivalent to @code{ffpe-trap=}@var{list1},@var{list2}.
 
 Note that once enabled an exception cannot be disabled (no negative form).