public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/106986] [10/11/12/13 Regression] ICE in simplify_findloc_nodim, at fortran/simplify.cc:5675
Date: Mon, 26 Sep 2022 18:13:12 +0000 [thread overview]
Message-ID: <bug-106986-4-ym6KBsRdY7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106986-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106986
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:50592ed4703d2e1ade2b197c58b72da0b91933cc
commit r11-10274-g50592ed4703d2e1ade2b197c58b72da0b91933cc
Author: Harald Anlauf <anlauf@gmx.de>
Date: Tue Sep 20 22:41:48 2022 +0200
Fortran: error recovery on invalid ARRAY argument to FINDLOC [PR106986]
gcc/fortran/ChangeLog:
PR fortran/106986
* simplify.c (gfc_simplify_findloc): Do not try to simplify
intrinsic FINDLOC when the ARRAY argument has a NULL shape.
gcc/testsuite/ChangeLog:
PR fortran/106986
* gfortran.dg/pr106986.f90: New test.
(cherry picked from commit 5976fbf9d5dd9542fcb82eebb2185886fd52d000)
next prev parent reply other threads:[~2022-09-26 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 17:35 [Bug fortran/106986] New: " gscfq@t-online.de
2022-09-20 19:03 ` [Bug fortran/106986] " anlauf at gcc dot gnu.org
2022-09-20 20:46 ` marxin at gcc dot gnu.org
2022-09-20 20:50 ` cvs-commit at gcc dot gnu.org
2022-09-20 20:58 ` anlauf at gcc dot gnu.org
2022-09-21 7:50 ` rguenth at gcc dot gnu.org
2022-09-22 18:48 ` cvs-commit at gcc dot gnu.org
2022-09-26 18:13 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-26 18:16 ` cvs-commit at gcc dot gnu.org
2022-09-26 18:19 ` anlauf at gcc dot gnu.org
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=bug-106986-4-ym6KBsRdY7@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).