> Cc: Eli Zaretskii <e...@gnu.org>, gcc@gcc.gnu.org, gcc-patc...@gcc.gnu.org,
> jos...@codesourcery.com
> From: Martin Liška <mli...@suse.cz>
> Date: Fri, 2 Jul 2021 11:40:06 +0200
>
> > It must
> > look sensible without that. In this case it seems that already the
> > generated .texinfo input to makeinfo is bad, where does the 'e' (or 'f')
> > come from? The original texinfo file simply contains:
>
> These are auto-numbered. Theoretically one can use the verbose anchor names:
>
> @anchor{demo cmdoption-Wshift-overflow3}@anchor{e}@anchor{demo
> cmdoption-wshift-overflow3}@anchor{f}
> @deffn {Option} @w{-}Wshift@w{-}overflow3=n, @w{-}Wshift@w{-}overflow3
>
> Default option value for @ref{e,,-Wshift-overflow3}.
>
> But these would lead to even longer '*note -Wshift-overflow3: demo
> cmdoption-wshift-overflow3' output.
While auto-numbering is a nice feature, the human-readable anchors
have an advantage of hinting on the topic to which the cross-reference
points.
