public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-9892] Daily bump.
Date: Thu, 21 Apr 2022 00:19:04 +0000 (GMT) [thread overview]
Message-ID: <20220421001904.1CD5A3858D1E@sourceware.org> (raw)
https://gcc.gnu.org/g:8f36ddeab7498414704789379d896ac179ba471e
commit r11-9892-g8f36ddeab7498414704789379d896ac179ba471e
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Thu Apr 21 00:18:25 2022 +0000
Daily bump.
Diff:
---
gcc/DATESTAMP | 2 +-
gcc/cp/ChangeLog | 11 +++++++++++
gcc/testsuite/ChangeLog | 8 ++++++++
3 files changed, 20 insertions(+), 1 deletion(-)
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 82f97c7205f..d4ff129236b 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220420
+20220421
diff --git a/gcc/cp/ChangeLog b/gcc/cp/ChangeLog
index 7123214e2f3..de844e6f298 100644
--- a/gcc/cp/ChangeLog
+++ b/gcc/cp/ChangeLog
@@ -1,3 +1,14 @@
+2022-04-20 Jakub Jelinek <jakub@redhat.com>
+
+ Backported from master:
+ 2022-04-19 Jakub Jelinek <jakub@redhat.com>
+
+ PR c++/105256
+ * typeck2.c (process_init_constructor_array,
+ process_init_constructor_record, process_init_constructor_union): Move
+ CONSTRUCTOR_PLACEHOLDER_BOUNDARY flag from CONSTRUCTOR elements to the
+ containing CONSTRUCTOR.
+
2022-04-12 Patrick Palka <ppalka@redhat.com>
Backported from master:
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index e5d8b923473..1c74f2b9405 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2022-04-20 Jakub Jelinek <jakub@redhat.com>
+
+ Backported from master:
+ 2022-04-19 Jakub Jelinek <jakub@redhat.com>
+
+ PR c++/105256
+ * g++.dg/cpp0x/pr105256.C: New test.
+
2022-04-19 Richard Biener <rguenther@suse.de>
Backported from master:
reply other threads:[~2022-04-21 0:19 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=20220421001904.1CD5A3858D1E@sourceware.org \
--to=gccadmin@gcc.gnu.org \
--cc=gcc-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).