public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 587564f3f1c48c90b07288ff68f383c4fbece348 Date: Fri, 15 Oct 2021 08:24:14 +0000 (GMT) [thread overview] Message-ID: <20211015082414.D85FC3857815@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 587564f3f1c48c90b07288ff68f383c4fbece348 (commit) from e1fb6157ee91f0dd04ec2b8d9f9d06df70860557 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 587564f3f1c48c90b07288ff68f383c4fbece348 Author: Richard Biener <rguenther@suse.de> Date: Fri Sep 10 09:26:22 2021 +0200 Add note that STABS is deprecated This amends the caveats section of the GCC 12 release notes according to the STABS deprecation. diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index f38fd2be..5be15700 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -62,6 +62,12 @@ a work-in-progress.</p> <code>m68k*-*-openbsd*</code> and <code>vax-*-openbsd*</code> configurations has been removed. </li> + <li> + <strong>STABS:</strong> + Support for emitting the STABS debugging format is deprecated and will + be removed in the next release. All ports now default to emit DWARF + (version 2 or later) debugging info or are obsoleted. + </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 6 ++++++ 1 file changed, 6 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-10-15 8:24 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=20211015082414.D85FC3857815@sourceware.org \ --to=rguenth@sourceware.org \ --cc=gcc-cvs-wwwdocs@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).