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] Simplify gcov-dump and lto-dump. Date: Mon, 24 May 2021 13:17:40 +0000 (GMT) [thread overview] Message-ID: <20210524131740.70F353891C10@sourceware.org> (raw) https://gcc.gnu.org/g:f146ba4d8a65ed8e4a98a49f7c733924ad3d6406 commit f146ba4d8a65ed8e4a98a49f7c733924ad3d6406 Author: Martin Liska <mliska@suse.cz> Date: Mon May 24 15:17:22 2021 +0200 Simplify gcov-dump and lto-dump. Diff: --- gcc/doc/gcov-dump.texi | 11 ----------- gcc/doc/lto-dump.texi | 11 ----------- 2 files changed, 22 deletions(-) diff --git a/gcc/doc/gcov-dump.texi b/gcc/doc/gcov-dump.texi index c9d23445cb9..ab76841c946 100644 --- a/gcc/doc/gcov-dump.texi +++ b/gcc/doc/gcov-dump.texi @@ -6,22 +6,11 @@ @node Gcov-dump @chapter @command{gcov-dump}---an Offline Gcda and Gcno Profile Dump Tool -@menu -* Gcov-dump Intro:: Introduction to gcov-dump. -* Invoking Gcov-dump:: How to use gcov-dump. -@end menu - -@node Gcov-dump Intro -@section Introduction to @command{gcov-dump} - @subsubheading Description @command{gcov-dump} is a tool you can use in conjunction with GCC to dump content of gcda and gcno profile files offline. -@node Invoking Gcov-dump -@section Invoking @command{gcov-dump} - @subsubheading Synopsis gcov-dump [@option{-v}|@option{--version}] diff --git a/gcc/doc/lto-dump.texi b/gcc/doc/lto-dump.texi index d05e32727d4..ff64137c0c7 100644 --- a/gcc/doc/lto-dump.texi +++ b/gcc/doc/lto-dump.texi @@ -6,22 +6,11 @@ @node lto-dump @chapter @command{lto-dump}---Tool for dumping LTO object files. -@menu -* lto-dump Intro:: Introduction to lto-dump. -* Invoking lto-dump:: How to use lto-dump. -@end menu - -@node lto-dump Intro -@section Introduction to @command{lto-dump} - @subsubheading Description @command{lto-dump} is a tool you can use in conjunction with GCC to dump link time optimization object files. -@node Invoking lto-dump -@section Invoking @command{lto-dump} - @smallexample Usage: lto-dump @r{[}@var{OPTION}@r{]} ... @var{objfiles} @end smallexample
reply other threads:[~2021-05-24 13:17 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=20210524131740.70F353891C10@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).