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/108529] [10/11/12 Regression] ICE in transformational_result, at fortran/simplify.cc:478
Date: Sun, 05 Feb 2023 18:55:31 +0000 [thread overview]
Message-ID: <bug-108529-4-f0Ok0MZuoO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108529-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108529
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:b66a0f2fecb4dc1ac5960ff5d630ab8f672b4106
commit r10-11198-gb66a0f2fecb4dc1ac5960ff5d630ab8f672b4106
Author: Harald Anlauf <anlauf@gmx.de>
Date: Tue Jan 24 21:39:43 2023 +0100
Fortran: ICE in transformational_result [PR108529]
gcc/fortran/ChangeLog:
PR fortran/108529
* simplify.c (simplify_transformation): Do not try to simplify
transformational intrinsic when the ARRAY argument has a NULL
shape.
gcc/testsuite/ChangeLog:
PR fortran/108529
* gfortran.dg/pr108529.f90: New test.
(cherry picked from commit 6c96382eed96a9285611f2e3e2e59557094172b8)
next prev parent reply other threads:[~2023-02-05 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 17:53 [Bug fortran/108529] New: [10/11/12/13 " gscfq@t-online.de
2023-01-24 19:39 ` [Bug fortran/108529] " anlauf at gcc dot gnu.org
2023-01-24 20:42 ` cvs-commit at gcc dot gnu.org
2023-01-24 20:48 ` anlauf at gcc dot gnu.org
2023-01-25 7:36 ` rguenth at gcc dot gnu.org
2023-01-28 21:38 ` [Bug fortran/108529] [10/11/12 " anlauf at gcc dot gnu.org
2023-01-28 22:03 ` cvs-commit at gcc dot gnu.org
2023-02-04 15:43 ` cvs-commit at gcc dot gnu.org
2023-02-05 18:55 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-05 18:57 ` 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-108529-4-f0Ok0MZuoO@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).