The generated gcc.1 man page contais a couple of weird texinfo artefacts,
I suppose the problem is in texi2pod.pl in most cases, but am not 100% sure.
1) @anchor{something} doesn't seem to be handled and makes it all the way
through into the man page (should it be just nuked for the man page?)
E.g. in:
-Wtrigraphs
@anchor{Wtrigraphs} Most trigraphs in comments cannot affect the
meaning of the program. However, a
2) @pxref{something} makes it all the way through into the man page too
E.g. in:
-Wno-deprecated-declarations
Do not warn about uses of functions, variables, and types marked as
deprecated by using the "deprecated"
attribute. (@pxref{Function Attributes}, @pxref{Variable
Attributes}, @pxref{Type Attributes}.)
3) @item is only handled at the beginning of line, so we have
@item max-inline-insns-single
is set to I<n>/2.
@item max-inline-insns-auto
is set to I<n>/2.
@item min-inline-insns
is set to 130 or I<n>/4, whichever is smaller.
@item max-inline-insns-rtl
is set to I<n>.
Perhaps this should be solved by removing the spaces in invoke.texi.
4) @samp{@@} in the texi source is transformed weirdly:
@samp{;}, and each switch starts with an @samp{@@} instead of the
@samp{-}, without spaces between multiple switches. This is supposed to
ease shell-processing.
becomes in gcc.pod:
B<;>, and each switch starts with an B<@} instead of the
@samp{->, without spaces between multiple switches. This is supposed to
ease shell-processing.
--
Summary: texi2pod issues
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jakub at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27832
