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-10333] Daily bump.
Date: Tue, 25 Oct 2022 00:21:16 +0000 (GMT) [thread overview]
Message-ID: <20221025002116.F2B4C3858C83@sourceware.org> (raw)
https://gcc.gnu.org/g:bd9dd33bdd00a0e80173000318c5f71a8d1eba20
commit r11-10333-gbd9dd33bdd00a0e80173000318c5f71a8d1eba20
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Tue Oct 25 00:20:38 2022 +0000
Daily bump.
Diff:
---
gcc/DATESTAMP | 2 +-
gcc/cp/ChangeLog | 8 ++++++++
gcc/testsuite/ChangeLog | 8 ++++++++
3 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 9c3fc6cabad..c75820ce08e 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20221024
+20221025
diff --git a/gcc/cp/ChangeLog b/gcc/cp/ChangeLog
index 92eb8fc1672..476ad3737e9 100644
--- a/gcc/cp/ChangeLog
+++ b/gcc/cp/ChangeLog
@@ -1,3 +1,11 @@
+2022-10-24 Marek Polacek <polacek@redhat.com>
+
+ Backported from master:
+ 2022-05-27 Marek Polacek <polacek@redhat.com>
+
+ PR c++/105725
+ * parser.c (class_decl_loc_t::add): Check CLASS_TYPE_P.
+
2022-07-22 Jason Merrill <jason@redhat.com>
PR c++/106361
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index eb24df5abc5..ad1cd37630e 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2022-10-24 Marek Polacek <polacek@redhat.com>
+
+ Backported from master:
+ 2022-05-27 Marek Polacek <polacek@redhat.com>
+
+ PR c++/105725
+ * g++.dg/warn/Wmismatched-tags-10.C: New test.
+
2022-10-23 Harald Anlauf <anlauf@gmx.de>
Backported from master:
reply other threads:[~2022-10-25 0:21 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=20221025002116.F2B4C3858C83@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).