public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. bb9f7874cd64ae96a8d800863cbfb077464533fc
Date: Thu, 7 May 2020 10:36:45 +0000 (GMT) [thread overview]
Message-ID: <20200507103645.AF8D7387084B@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 bb9f7874cd64ae96a8d800863cbfb077464533fc (commit)
from ebbb2e8e5041a55800ae277d112e9081c89f5811 (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 bb9f7874cd64ae96a8d800863cbfb077464533fc
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu May 7 12:36:31 2020 +0200
Releasing 10.1.
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index ca0761ff..465de075 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -24,9 +24,6 @@ You may also want to check out our
</p>
-<p>Note: GCC 10 has not been released yet, so this document is
-a work-in-progress.</p>
-
<!-- .................................................................. -->
<h2>Caveats</h2>
<ul>
@@ -1006,7 +1003,15 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512)));
</ul>
<!-- .................................................................. -->
-<!-- <h2><a name="10.1">GCC 10.1</a></h2> -->
+<h2><a name="10.1">GCC 10.1</a></h2>
+
+<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=10.0">list
+of problem reports (PRs)</a> from GCC's bug tracking system that are
+known to be fixed in the 10.1 release. This list might not be
+complete (that is, it is possible that some PRs that have been fixed
+are not listed here).</p>
+
+<!-- .................................................................. -->
</body>
</html>
diff --git a/htdocs/gcc-10/index.html b/htdocs/gcc-10/index.html
new file mode 100644
index 00000000..98c10074
--- /dev/null
+++ b/htdocs/gcc-10/index.html
@@ -0,0 +1,57 @@
+<!DOCTYPE html>
+<html lang="en">
+
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>GCC 10 Release Series</title>
+<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" />
+</head>
+
+<body>
+
+<h1>GCC 10 Release Series</h1>
+
+<p>May 7, 2020</p>
+
+<p>The <a href="http://www.gnu.org">GNU project</a> and the GCC
+developers are pleased to announce the release of GCC 10.1.</p>
+
+<p>This release is a major release, containing new features (as well
+as many other improvements) relative to GCC 9.x.</p>
+
+<h2>Release History</h2>
+
+<dl>
+
+<dt>GCC 10.1</dt>
+<dd>May 7, 2020
+ (<a href="changes.html">changes</a>,
+ <a href="http://gcc.gnu.org/onlinedocs/10.1.0/">documentation</a>)
+</dd>
+
+</dl>
+
+<h2>References and Acknowledgements</h2>
+
+<p>GCC used to stand for the GNU C Compiler, but since the compiler
+supports several other languages aside from C, it now stands for the
+GNU Compiler Collection.</p>
+
+<p>A list of <a href="buildstat.html">successful builds</a> is updated
+as new information becomes available.</p>
+
+<p>The GCC developers would like to thank the numerous people that have
+contributed new features, improvements, bug fixes, and other changes as
+well as test results to GCC.
+This <a href="http://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Contributors.html">amazing
+group of volunteers</a> is what makes GCC successful.</p>
+
+<p>For additional information about GCC please refer to the
+<a href="../index.html">GCC project web site</a> or contact the
+<a href="mailto:gcc@gcc.gnu.org">GCC development mailing list</a>.</p>
+
+<p>To obtain GCC please use <a href="../mirrors.html">our mirror sites</a>
+or <a href="../git.html">our version control system</a>.</p>
+
+</body>
+</html>
-----------------------------------------------------------------------
Summary of changes:
htdocs/gcc-10/changes.html | 13 +++++++++----
htdocs/{gcc-4.1 => gcc-10}/index.html | 34 +++++++++++-----------------------
2 files changed, 20 insertions(+), 27 deletions(-)
copy htdocs/{gcc-4.1 => gcc-10}/index.html (64%)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2020-05-07 10:36 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=20200507103645.AF8D7387084B@sourceware.org \
--to=jakub@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).