public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. bc20d66ff363103abbb9e317199c68e96a924690 Date: Thu, 15 Oct 2020 10:41:48 +0000 (GMT) [thread overview] Message-ID: <20201015104148.74C283857804@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 bc20d66ff363103abbb9e317199c68e96a924690 (commit) from d7f86129184f9981930148fbe1a5e5075abcef02 (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 bc20d66ff363103abbb9e317199c68e96a924690 Author: David Malcolm <dmalcolm@redhat.com> Date: Wed Oct 7 06:15:47 2020 -0400 gcc-11/changes: C++11 is now required to build GCC This summarizes GCC 11's change in build requirements from C++98 to C++11, for the release notes. I've based it on the change to gcc/doc/install.texi in the GCC source tree, which was 5329b59a2e13dabbe2038af0fe2e3cf5fc7f98ed there. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 37b9127a..817687e4 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -35,6 +35,11 @@ a work-in-progress.</p> features with <code>-fno-new-ttp-matching</code>. </li> + <li>When building GCC itself, the host compiler must now support C++11, + rather than C++98. In particular bootstrapping GCC 11 using an older + version of GCC requires a binary of GCC 4.8 or later, rather than of + GCC 3.4 or later as was the case for bootstrapping GCC 10.</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 <code>-dumpbase</code>, ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 5 +++++ 1 file changed, 5 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-10-15 10: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=20201015104148.74C283857804@sourceware.org \ --to=dmalcolm@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).