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 r13-8671] Daily bump.
Date: Thu,  2 May 2024 00:22:08 +0000 (GMT)	[thread overview]
Message-ID: <20240502002208.D0F9B3858D34@sourceware.org> (raw)

https://gcc.gnu.org/g:17e11119e083eeffb7f20158b62826931c28e0e0

commit r13-8671-g17e11119e083eeffb7f20158b62826931c28e0e0
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Thu May 2 00:21:41 2024 +0000

    Daily bump.

Diff:
---
 gcc/DATESTAMP           |  2 +-
 gcc/cp/ChangeLog        | 34 ++++++++++++++++++++++++++++++++++
 gcc/testsuite/ChangeLog | 32 ++++++++++++++++++++++++++++++++
 3 files changed, 67 insertions(+), 1 deletion(-)

diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 3424846c2ca..1453ab15983 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20240501
+20240502
diff --git a/gcc/cp/ChangeLog b/gcc/cp/ChangeLog
index 18df074fe66..d3eb9a6f2de 100644
--- a/gcc/cp/ChangeLog
+++ b/gcc/cp/ChangeLog
@@ -1,3 +1,37 @@
+2024-05-01  Patrick Palka  <ppalka@redhat.com>
+
+	PR c++/113141
+	* call.cc (reference_binding): Remove badness criteria sanity
+	check in the recursive case.
+
+2024-05-01  centurion  <centurion009@proton.me>
+
+	Backported from master:
+	2024-04-04  centurion  <centurion009@proton.me>
+
+	PR c++/114377
+	* pt.cc (find_template_parameter_info::found): Use TREE_TYPE for
+	TEMPLATE_DECL instead of DECL_INITIAL.
+
+2024-05-01  Jason Merrill  <jason@redhat.com>
+
+	Backported from master:
+	2024-04-02  Jason Merrill  <jason@redhat.com>
+
+	PR c++/114561
+	PR c++/114562
+	* call.cc (convert_like_internal): Avoid adding qualification
+	conversion in direct reference binding.
+
+2024-05-01  Jason Merrill  <jason@redhat.com>
+
+	Backported from master:
+	2024-03-28  Jason Merrill  <jason@redhat.com>
+
+	PR c++/100667
+	* semantics.cc (same_type_ref_bind_p): New.
+	(finish_trait_expr): Use it.
+
 2024-04-21  Jakub Jelinek  <jakub@redhat.com>
 
 	Backported from master:
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 3d939becaa1..fe84bfa0502 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,35 @@
+2024-05-01  Patrick Palka  <ppalka@redhat.com>
+
+	PR c++/113141
+	* g++.dg/conversion/ref12.C: New test.
+	* g++.dg/cpp0x/initlist-ref1.C: new test.
+
+2024-05-01  centurion  <centurion009@proton.me>
+
+	Backported from master:
+	2024-04-04  centurion  <centurion009@proton.me>
+
+	PR c++/114377
+	* g++.dg/cpp2a/class-deduction-alias19.C: New test.
+
+2024-05-01  Jason Merrill  <jason@redhat.com>
+
+	Backported from master:
+	2024-04-02  Jason Merrill  <jason@redhat.com>
+
+	PR c++/114561
+	PR c++/114562
+	* g++.dg/conversion/ref10.C: New test.
+	* g++.dg/conversion/ref11.C: New test.
+
+2024-05-01  Jason Merrill  <jason@redhat.com>
+
+	Backported from master:
+	2024-03-28  Jason Merrill  <jason@redhat.com>
+
+	PR c++/100667
+	* g++.dg/ext/is_constructible8.C: New test.
+
 2024-04-30  Joe Ramsay  <Joe.Ramsay@arm.com>
 
 	Backported from master:

                 reply	other threads:[~2024-05-02  0:22 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=20240502002208.D0F9B3858D34@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).