public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/sphinx] Update man-pages related texi files. Date: Mon, 24 May 2021 12:55:13 +0000 (GMT) [thread overview] Message-ID: <20210524125513.6B4843858034@sourceware.org> (raw) https://gcc.gnu.org/g:cab6050fa9f02bf444f48d4bbf3d8f0c1bf401ed commit cab6050fa9f02bf444f48d4bbf3d8f0c1bf401ed Author: Martin Liska <mliska@suse.cz> Date: Mon May 24 14:54:53 2021 +0200 Update man-pages related texi files. Diff: --- gcc/doc/gcov-dump.texi | 18 ++++++------------ gcc/doc/lto-dump.texi | 42 ++++++------------------------------------ 2 files changed, 12 insertions(+), 48 deletions(-) diff --git a/gcc/doc/gcov-dump.texi b/gcc/doc/gcov-dump.texi index 6b5353cea81..c9d23445cb9 100644 --- a/gcc/doc/gcov-dump.texi +++ b/gcc/doc/gcov-dump.texi @@ -22,20 +22,14 @@ dump content of gcda and gcno profile files offline. @node Invoking Gcov-dump @section Invoking @command{gcov-dump} -@smallexample -Usage: gcov-dump @r{[}@var{OPTION}@r{]} ... @var{gcovfiles} -@end smallexample - -@command{gcov-dump} accepts the following options: - @subsubheading Synopsis -gcov-dump [@emph{-v}|@emph{--version}] - [@emph{-h}|@emph{--help}] - [@emph{-l}|@emph{--long}] - [@emph{-p}|@emph{--positions}] - [@emph{-r}|@emph{--raw}] - [@emph{gcovfiles}] +gcov-dump [@option{-v}|@option{--version}] + [@option{-h}|@option{--help}] + [@option{-l}|@option{--long}] + [@option{-p}|@option{--positions}] + [@option{-r}|@option{--raw}] + [@var{gcovfiles}] @subsubheading Options diff --git a/gcc/doc/lto-dump.texi b/gcc/doc/lto-dump.texi index e1909c4cab6..d05e32727d4 100644 --- a/gcc/doc/lto-dump.texi +++ b/gcc/doc/lto-dump.texi @@ -2,32 +2,6 @@ @c This is part of the GCC manual. @c For copying conditions, see the file gcc.texi. -@ignore -@c man begin COPYRIGHT -Copyright @copyright{} 2017-2021 Free Software Foundation, Inc. - -Permission is granted to copy, distribute and/or modify this document -under the terms of the GNU Free Documentation License, Version 1.3 or -any later version published by the Free Software Foundation; with the -Invariant Sections being ``GNU General Public License'' and ``Funding -Free Software'', the Front-Cover texts being (a) (see below), and with -the Back-Cover Texts being (b) (see below). A copy of the license is -included in the gfdl(7) man page. - -(a) The FSF's Front-Cover Text is: - - A GNU Manual - -(b) The FSF's Back-Cover Text is: - - You have freedom to copy and modify this GNU Manual, like GNU - software. Copies published by the Free Software Foundation raise - funds for GNU development. -@c man end -@c Set file name and title for the man page. -@setfilename lto-dump -@settitle Tool for dumping LTO object files. -@end ignore @node lto-dump @chapter @command{lto-dump}---Tool for dumping LTO object files. @@ -39,13 +13,12 @@ included in the gfdl(7) man page. @node lto-dump Intro @section Introduction to @command{lto-dump} -@c man begin DESCRIPTION + +@subsubheading Description @command{lto-dump} is a tool you can use in conjunction with GCC to dump link time optimization object files. -@c man end - @node Invoking lto-dump @section Invoking @command{lto-dump} @@ -55,8 +28,8 @@ Usage: lto-dump @r{[}@var{OPTION}@r{]} ... @var{objfiles} @command{lto-dump} accepts the following options: -@ignore -@c man begin SYNOPSIS +@subsubheading Synopsis + lto-dump [@option{-list}] [@option{-demangle}] [@option{-defined-only}] @@ -73,10 +46,9 @@ lto-dump [@option{-list}] [@option{-dump-level=}] [@option{-dump-body=}] [@option{-help}] @var{lto-dump} -@c man end -@end ignore -@c man begin OPTIONS +@subsubheading Options + @table @gcctabopt @item -list Dumps list of details of functions and variables. @@ -127,5 +99,3 @@ Dump the specific gimple body. Display the dump tool help. @end table - -@c man end
reply other threads:[~2021-05-24 12:55 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210524125513.6B4843858034@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).