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-9245] Daily bump.
Date: Mon, 13 Mar 2023 00:21:57 +0000 (GMT)	[thread overview]
Message-ID: <20230313002157.204AC3858D32@sourceware.org> (raw)

https://gcc.gnu.org/g:378e677bf5cb5bebb4a80da8c11aed477f4057c4

commit r12-9245-g378e677bf5cb5bebb4a80da8c11aed477f4057c4
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Mon Mar 13 00:21:17 2023 +0000

    Daily bump.

Diff:
---
 gcc/DATESTAMP         |  2 +-
 gcc/fortran/ChangeLog | 24 ++++++++++++++++++++++++
 2 files changed, 25 insertions(+), 1 deletion(-)

diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 4ce3ea7c20f..356057bf73a 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20230312
+20230313
diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog
index a788d34f0d9..0b364eb929f 100644
--- a/gcc/fortran/ChangeLog
+++ b/gcc/fortran/ChangeLog
@@ -1,3 +1,27 @@
+2023-03-12  Mikael Morin  <mikael@gcc.gnu.org>
+
+	Backported from master:
+	2023-02-25  Mikael Morin  <mikael@gcc.gnu.org>
+
+	PR fortran/108923
+	* intrinsic.cc (get_intrinsic_dummy_arg,
+	set_intrinsic_dummy_arg): Rename the former to the latter.
+	Remove the return value, add a reference to the lhs as argument,
+	and do the pointer assignment inside the function.  Don't do
+	it if the pointer is already non-NULL.
+	(sort_actual): Update caller.
+
+2023-03-12  Mikael Morin  <mikael@gcc.gnu.org>
+
+	Backported from master:
+	2023-02-24  Mikael Morin  <mikael@gcc.gnu.org>
+
+	PR fortran/108923
+	* expr.cc (gfc_free_actual_arglist): Free associated_dummy
+	memory.
+	(gfc_copy_actual_arglist): Make a copy of the associated_dummy
+	field if it is set in the original element.
+
 2023-03-08  Tobias Burnus  <tobias@codesourcery.com>
 
 	Backported from master:

                 reply	other threads:[~2023-03-13  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=20230313002157.204AC3858D32@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).