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(refs/users/marxin/heads/stabs-removal)] Remove from docs. Date: Wed, 24 Aug 2022 14:54:35 +0000 (GMT) [thread overview] Message-ID: <20220824145435.7C70F3853804@sourceware.org> (raw) https://gcc.gnu.org/g:57d7ddbfef6894fbb9b4683b159257612c8624e4 commit 57d7ddbfef6894fbb9b4683b159257612c8624e4 Author: Martin Liska <mliska@suse.cz> Date: Wed Aug 24 16:54:16 2022 +0200 Remove from docs. Diff: --- gcc/doc/invoke.texi | 2 +- gcc/doc/passes.texi | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 3359313d9c5..c9486ed1aaf 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -45,7 +45,7 @@ remainder. @command{g++} accepts mostly the same options as @command{gcc}. @c man end @c man begin SEEALSO gpl(7), gfdl(7), fsf-funding(7), -cpp(1), gcov(1), as(1), ld(1), gdb(1), dbx(1) +cpp(1), gcov(1), as(1), ld(1), gdb(1) and the Info entries for @file{gcc}, @file{cpp}, @file{as}, @file{ld}, @file{binutils} and @file{gdb}. @c man end diff --git a/gcc/doc/passes.texi b/gcc/doc/passes.texi index 1e821d4e513..9e8b4f50ad6 100644 --- a/gcc/doc/passes.texi +++ b/gcc/doc/passes.texi @@ -1184,7 +1184,7 @@ these files. This is run after final because it must output the stack slot offsets for pseudo registers that did not get hard registers. Source files -are @file{dbxout.cc} for DBX symbol table format, @file{dwarfout.c} for +are @file{dwarfout.c} for DWARF symbol table format, files @file{dwarf2out.cc} and @file{dwarf2asm.cc} for DWARF2 symbol table format, and @file{vmsdbgout.cc} for VMS debug symbol table format.
next reply other threads:[~2022-08-24 14:54 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-24 14:54 Martin Liska [this message] 2022-08-25 6:54 Martin Liska
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=20220824145435.7C70F3853804@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).