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 r12-8476] Daily bump.
Date: Tue, 14 Jun 2022 00:19:46 +0000 (GMT) [thread overview]
Message-ID: <20220614001946.28556384B838@sourceware.org> (raw)
https://gcc.gnu.org/g:2d45d5df9ad00ea4ce9e2d9fe52a87b298a77cf9
commit r12-8476-g2d45d5df9ad00ea4ce9e2d9fe52a87b298a77cf9
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Tue Jun 14 00:19:10 2022 +0000
Daily bump.
Diff:
---
gcc/DATESTAMP | 2 +-
gcc/d/ChangeLog | 12 ++++++++++++
gcc/testsuite/ChangeLog | 7 +++++++
3 files changed, 20 insertions(+), 1 deletion(-)
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 1d9796c2616..f6e8eb7c21b 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220613
+20220614
diff --git a/gcc/d/ChangeLog b/gcc/d/ChangeLog
index bb39463849b..1fa18200029 100644
--- a/gcc/d/ChangeLog
+++ b/gcc/d/ChangeLog
@@ -1,3 +1,15 @@
+2022-06-13 Iain Buclaw <ibuclaw@gdcproject.org>
+
+ Backported from master:
+ 2022-06-13 Iain Buclaw <ibuclaw@gdcproject.org>
+
+ * d-tree.h (check_typeinfo_type): Add Expression* parameter.
+ (build_typeinfo): Likewise. Declare new override.
+ * expr.cc (ExprVisitor): Call build_typeinfo with Expression*.
+ * typeinfo.cc (check_typeinfo_type): Include expression in the
+ diagnostic message.
+ (build_typeinfo): New override.
+
2022-05-31 Iain Buclaw <ibuclaw@gdcproject.org>
Backported from master:
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 214f9f458ba..db4d5437934 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,10 @@
+2022-06-13 Iain Buclaw <ibuclaw@gdcproject.org>
+
+ Backported from master:
+ 2022-06-13 Iain Buclaw <ibuclaw@gdcproject.org>
+
+ * gdc.dg/rtti1.d: New test.
+
2022-06-11 Patrick Palka <ppalka@redhat.com>
Backported from master:
reply other threads:[~2022-06-14 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=20220614001946.28556384B838@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).