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 one documentation entry. Date: Thu, 25 Aug 2022 07:23:53 +0000 (GMT) [thread overview] Message-ID: <20220825072353.1A817385ED4D@sourceware.org> (raw) https://gcc.gnu.org/g:a6b2704f14d69039033ce0a839e4ea48854c9d58 commit a6b2704f14d69039033ce0a839e4ea48854c9d58 Author: Martin Liska <mliska@suse.cz> Date: Thu Aug 25 09:22:01 2022 +0200 Remove one documentation entry. Diff: --- gcc/doc/tm.texi | 2 +- gcc/doc/tm.texi.in | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index cc7769b6515..32ed04b6eaf 100644 --- a/gcc/doc/tm.texi +++ b/gcc/doc/tm.texi @@ -9967,7 +9967,7 @@ A C expression that returns the type of debugging output GCC should produce when the user specifies just @option{-g}. Define this if you have arranged for GCC to support more than one format of debugging output. Currently, the allowable values are -@code{DWARF2_DEBUG}, @code{XCOFF_DEBUG}, @code{VMS_DEBUG}, +@code{DWARF2_DEBUG}, @code{VMS_DEBUG}, and @code{VMS_AND_DWARF2_DEBUG}. When the user specifies @option{-ggdb}, GCC normally also uses the diff --git a/gcc/doc/tm.texi.in b/gcc/doc/tm.texi.in index 0d769cd3a96..be7d229e3ee 100644 --- a/gcc/doc/tm.texi.in +++ b/gcc/doc/tm.texi.in @@ -6654,7 +6654,7 @@ A C expression that returns the type of debugging output GCC should produce when the user specifies just @option{-g}. Define this if you have arranged for GCC to support more than one format of debugging output. Currently, the allowable values are -@code{DWARF2_DEBUG}, @code{XCOFF_DEBUG}, @code{VMS_DEBUG}, +@code{DWARF2_DEBUG}, @code{VMS_DEBUG}, and @code{VMS_AND_DWARF2_DEBUG}. When the user specifies @option{-ggdb}, GCC normally also uses the
next reply other threads:[~2022-08-25 7:23 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-25 7:23 Martin Liska [this message] 2022-08-25 7:33 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=20220825072353.1A817385ED4D@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).