public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r11-6350] Daily bump.
Date: Mon, 28 Dec 2020 00:17:00 +0000 (GMT)	[thread overview]
Message-ID: <20201228001700.1B2023870855@sourceware.org> (raw)

https://gcc.gnu.org/g:adfe99ad8faa4755d27c0f5981e72191f211ec7d

commit r11-6350-gadfe99ad8faa4755d27c0f5981e72191f211ec7d
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Mon Dec 28 00:16:28 2020 +0000

    Daily bump.

Diff:
---
 gcc/ChangeLog           |  5 +++++
 gcc/DATESTAMP           |  2 +-
 gcc/fortran/ChangeLog   | 11 +++++++++++
 gcc/testsuite/ChangeLog | 11 +++++++++++
 libstdc++-v3/ChangeLog  | 10 ++++++++++
 5 files changed, 38 insertions(+), 1 deletion(-)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 0f5253b22e9..f62619d62aa 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2020-12-27  Gerald Pfeifer  <gerald@pfeifer.com>
+
+	* doc/analyzer.texi (Analyzer Internals): Find a new source for
+	the "A Memory Model for Static Analysis of C Programs" paper.
+
 2020-12-25  Gerald Pfeifer  <gerald@pfeifer.com>
 
 	* doc/invoke.texi (C++ Module Mapper): Fix reference to libcody.
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index b7f012f6fde..1ace328d281 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20201227
+20201228
diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog
index c10f28737be..178d4cf2e06 100644
--- a/gcc/fortran/ChangeLog
+++ b/gcc/fortran/ChangeLog
@@ -1,3 +1,14 @@
+2020-12-27  Paul Thomas  <pault@gcc.gnu.org>
+
+	PR fortran/97694
+	PR fortran/97723
+	* check.c (allocatable_check): Select rank temporaries are
+	permitted even though they are treated as associate variables.
+	* resolve.c (gfc_resolve_code): Break on select rank as well as
+	select type so that the block os resolved.
+	* trans-stmt.c (trans_associate_var): Class associate variables
+	that are optional dummies must use the backend_decl.
+
 2020-12-26  Paul Thomas  <pault@gcc.gnu.org>
 
 	PR fortran/98022
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 3d36d641981..8af21450542 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,14 @@
+2020-12-27  Jeff Law  <law@redhat.com>
+
+	* gcc.dg/tree-ssa/asm-2.c: Use different register for iq2000.
+	* gcc.dg/tree-ssa/asm-3.c: Likewise.
+
+2020-12-27  Paul Thomas  <pault@gcc.gnu.org>
+
+	PR fortran/97694
+	PR fortran/97723
+	* gfortran.dg/select_rank_5.f90: New test.
+
 2020-12-26  Iain Sandoe  <iain@sandoe.co.uk>
 
 	PR c++/96045
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index dfc97005e05..5b6b170834e 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,13 @@
+2020-12-27  Gerald Pfeifer  <gerald@pfeifer.com>
+
+	* doc/xml/manual/abi.xml: Update link to Arm ABI.
+	* doc/html/manual/abi.html: Regenerate.
+
+2020-12-27  Gerald Pfeifer  <gerald@pfeifer.com>
+
+	* doc/xml/manual/debug.xml: Move Valgrind references to https.
+	* doc/html/manual/debug.html: Regenerate.
+
 2020-12-26  Gerald Pfeifer  <gerald@pfeifer.com>
 
 	* doc/xml/manual/abi.xml: Update link to Intel's compatibility


                 reply	other threads:[~2020-12-28  0:17 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=20201228001700.1B2023870855@sourceware.org \
    --to=gccadmin@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).