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-9653] Daily bump.
Date: Mon, 14 Mar 2022 00:18:58 +0000 (GMT) [thread overview]
Message-ID: <20220314001858.4BE2C3858C78@sourceware.org> (raw)
https://gcc.gnu.org/g:bf4ba41e8039d0603ead0dce8f43454300c9d6c5
commit r11-9653-gbf4ba41e8039d0603ead0dce8f43454300c9d6c5
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Mon Mar 14 00:18:15 2022 +0000
Daily bump.
Diff:
---
gcc/DATESTAMP | 2 +-
gcc/fortran/ChangeLog | 10 ++++++++++
gcc/testsuite/ChangeLog | 8 ++++++++
3 files changed, 19 insertions(+), 1 deletion(-)
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 6a00f110593..48ea82f86bf 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220313
+20220314
diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog
index b6ff4779086..f57d9adf17d 100644
--- a/gcc/fortran/ChangeLog
+++ b/gcc/fortran/ChangeLog
@@ -1,3 +1,13 @@
+2022-03-13 Harald Anlauf <anlauf@gmx.de>
+
+ Backported from master:
+ 2022-03-08 Harald Anlauf <anlauf@gmx.de>
+
+ PR fortran/104811
+ * frontend-passes.c (optimize_minmaxloc): Do not attempt
+ frontend-optimization of MINLOC/MAXLOC for character arrays, as
+ there is no suitable code yet for inline expansion.
+
2022-02-23 Harald Anlauf <anlauf@gmx.de>
Backported from master:
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 3b71f1469e3..f6b776a115a 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2022-03-13 Harald Anlauf <anlauf@gmx.de>
+
+ Backported from master:
+ 2022-03-08 Harald Anlauf <anlauf@gmx.de>
+
+ PR fortran/104811
+ * gfortran.dg/minmaxloc_16.f90: New test.
+
2022-03-11 Michael Meissner <meissner@the-meissners.org>
PR target/99708
reply other threads:[~2022-03-14 0:18 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=20220314001858.4BE2C3858C78@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).