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-11312] Daily bump.
Date: Mon,  8 Apr 2024 12:17:29 +0000 (GMT)	[thread overview]
Message-ID: <20240408121729.368F23858D39@sourceware.org> (raw)

https://gcc.gnu.org/g:8b910e5a64a5e1a264bb8bd69fe8409d8b37ec41

commit r11-11312-g8b910e5a64a5e1a264bb8bd69fe8409d8b37ec41
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Mon Apr 8 12:17:08 2024 +0000

    Daily bump.

Diff:
---
 gcc/DATESTAMP           |  2 +-
 gcc/fortran/ChangeLog   | 19 +++++++++++++++++++
 gcc/testsuite/ChangeLog | 16 ++++++++++++++++
 3 files changed, 36 insertions(+), 1 deletion(-)

diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index c21b6317f1e..1c86cd975ee 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20240405
+20240408
diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog
index 797ee2b53c1..4dd49e4e611 100644
--- a/gcc/fortran/ChangeLog
+++ b/gcc/fortran/ChangeLog
@@ -1,3 +1,22 @@
+2024-04-06  Harald Anlauf  <anlauf@gmx.de>
+
+	Backported from master:
+	2024-03-28  Harald Anlauf  <anlauf@gmx.de>
+
+	PR fortran/114474
+	* primary.c (gfc_variable_attr): Catch variables used in structure
+	constructors within DATA statements that are still tagged with a
+	temporary type BT_PROCEDURE from match_actual_arg and which have the
+	target attribute, and fix their typespec.
+
+2024-04-05  Chung-Lin Tang  <cltang@codesourcery.com>
+
+	Backported from master:
+	2021-12-03  Tobias Burnus  <tobias@codesourcery.com>
+
+	* trans-stmt.c (gfc_trans_allocate): Set e3_has_nodescriptor to true
+	only for non-named arrays.
+
 2024-04-02  Mikael Morin  <mikael@gcc.gnu.org>
 
 	Backported from master:
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index c5e03811dfc..b703e3c2ab1 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,19 @@
+2024-04-06  Harald Anlauf  <anlauf@gmx.de>
+
+	Backported from master:
+	2024-03-28  Harald Anlauf  <anlauf@gmx.de>
+
+	PR fortran/114474
+	* gfortran.dg/data_pointer_3.f90: New test.
+
+2024-04-05  Chung-Lin Tang  <cltang@codesourcery.com>
+
+	Backported from master:
+	2021-12-03  Tobias Burnus  <tobias@codesourcery.com>
+
+	* gfortran.dg/allocate_with_source_26.f90: Adjust testcase.
+	* gfortran.dg/allocate_with_mold_4.f90: New testcase.
+
 2024-04-02  Qing Zhao  <qing.zhao@oracle.com>
 
 	Backported from master:

                 reply	other threads:[~2024-04-08 12: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=20240408121729.368F23858D39@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).