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. dc78a1aaaeab65cb59d078b565b470c8dcc515d0
Date: Wed, 29 Jul 2020 13:41:19 +0000 (GMT)	[thread overview]
Message-ID: <20200729134119.D8C4E38708CA@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  dc78a1aaaeab65cb59d078b565b470c8dcc515d0 (commit)
      from  24cfad160b8ea25326e02f36f41e6d38dbd09073 (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 dc78a1aaaeab65cb59d078b565b470c8dcc515d0
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Jul 29 15:39:42 2020 +0200

    Document -gsplit-dwarf behavioral change
    
    This mentions that -gsplit-dwarf now requires -g to enable debug info
    generation.
    
            * gcc-11/changes.html: Mention -gsplit-dwarf behavioral change.

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index d3fb9882..96955345 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -43,6 +43,9 @@ a work-in-progress.</p>
       See <a href="https://gcc.gnu.org/pipermail/gcc-patches/2020-May/546494.html">the
       patch</a>, particularly its textual description, for more
       details about the changes.</li>
+
+  <li><code>-gsplit-dwarf</code> no longer enables debug info generation
+      on its own but requires a separate <code>-g</code> for this.</li>
 </ul>
 
 

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-11/changes.html | 3 +++
 1 file changed, 3 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-07-29 13:41 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=20200729134119.D8C4E38708CA@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: link
Be 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).