public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 57a146a0ce26e9eef1ecc1034689edb4c5412c3f
Date: Tue, 26 May 2020 08:09:32 +0000 (GMT)	[thread overview]
Message-ID: <20200526080932.E4A69385DC0A@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  57a146a0ce26e9eef1ecc1034689edb4c5412c3f (commit)
      from  15d62b0022c3f77aae1b7a5a7512e1692f0f17f7 (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 57a146a0ce26e9eef1ecc1034689edb4c5412c3f
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Tue May 26 05:02:16 2020 -0300

    gcc-11/changes: -dump* and -aux* revamp

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index e88a628a..2f00d1f1 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -30,7 +30,15 @@ a work-in-progress.</p>
 <!-- .................................................................. -->
 <h2>Caveats</h2>
 <ul>
-  <li>...</li>
+  <li>Naming and location of auxiliary and dump output files changed.
+      If you compile multiple input files in a single command, if you
+      enable Link Time Optimization, or if you use -dumpbase,
+      -dumpdir, -save-temps=*, and you expect any file other than the
+      primary output file(s) to be created as a side effect, watch out
+      for improvements and a few surprises.
+      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>
 </ul>
 
 

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-05-26  8:09 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=20200526080932.E4A69385DC0A@sourceware.org \
    --to=aoliva@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).