From: Arsen Arsenović <aarsenovic@baylibre.com>
Date: Thu, 20 Nov 2025 11:17:38 +0000 (+0100)
Subject: gcc/doc: Fix usages of @itemize with named items in Regs and Memory
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0b74386b61a05a45cf16bd09eb566e189bd21987;p=thirdparty%2Fgcc.git

gcc/doc: Fix usages of @itemize with named items in Regs and Memory

The old usage lead to makeinfo emitting text like "pseudo registers This
is the most common case. Most subregs have pseudo regs as their first
operand." when, clearly, "pseudo registers" was intended to be the name
of an item, and the rest of the paragraph a description.  This is
because @itemize was used, which does not support "naming" items.

Now, the paragraph used as an example above looks like this:

  pseudo registers
       This is the most common case.  Most ‘subreg’s have pseudo
       ‘reg’s as their first operand.

gcc/ChangeLog:

	* doc/rtl.texi (Regs and Memory): Use @table instead of @itemize
	for lists with named items.
---

diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi
index 089bb1c4ede..3ab83c352fe 100644
--- a/gcc/doc/rtl.texi
+++ b/gcc/doc/rtl.texi
@@ -2066,7 +2066,8 @@ enclosed in a @code{subreg}.
 
 There are currently three supported types for the first operand of a
 @code{subreg}:
-@itemize
+
+@table @asis
 @item pseudo registers
 This is the most common case.  Most @code{subreg}s have pseudo
 @code{reg}s as their first operand.
@@ -2096,7 +2097,7 @@ It is seldom necessary to wrap hard registers in @code{subreg}s; such
 registers would normally reduce to a single @code{reg} rtx.  This use of
 @code{subreg}s is discouraged and may not be supported in the future.
 
-@end itemize
+@end table
 
 @code{subreg}s of @code{subreg}s are not supported.  Using
 @code{simplify_gen_subreg} is the recommended way to avoid this problem.
@@ -2123,7 +2124,7 @@ defined.
 
 The high-order bits of rvalues are defined in the following circumstances:
 
-@itemize
+@table @asis
 @item @code{subreg}s of @code{mem}
 When @var{m2} is smaller than a word, the macro @code{LOAD_EXTEND_OP},
 can control how the high-order bits are defined.
@@ -2134,7 +2135,7 @@ The upper bits are defined when @code{SUBREG_PROMOTED_VAR_P} is true.
 Such subregs usually represent local variables, register variables
 and parameter pseudo variables that have been promoted to a wider mode.
 
-@end itemize
+@end table
 
 @var{bytenum} is always zero for a paradoxical @code{subreg}, even on
 big-endian targets.