public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105813] ICE in gfc_simplify_unpack, at fortran/simplify.cc:8490
Date: Thu, 23 Jun 2022 22:07:34 +0000 [thread overview]
Message-ID: <bug-105813-4-xWBuSDvyvI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105813-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105813
--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Jun 23, 2022 at 09:18:40PM +0000, anlauf at gcc dot gnu.org wrote:
>
> --- Comment #2 from anlauf at gcc dot gnu.org ---
> Simpler fix:
>
> diff --git a/gcc/fortran/check.cc b/gcc/fortran/check.cc
> index 0c2cb50c6a7..91d87a1b2c1 100644
> --- a/gcc/fortran/check.cc
> +++ b/gcc/fortran/check.cc
> @@ -6353,6 +6353,8 @@ gfc_check_unpack (gfc_expr *vector, gfc_expr *mask,
> gfc_expr *field)
> if (!same_type_check (vector, 0, field, 2))
> return false;
>
> + gfc_simplify_expr (mask, 0);
> +
> if (mask->expr_type == EXPR_ARRAY
> && gfc_array_size (vector, &vector_size))
> {
>
If it survives regression testing, then I think it
can be committed.
next prev parent reply other threads:[~2022-06-23 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 3:56 [Bug fortran/105813] New: " asolokha at gmx dot com
2022-06-02 14:48 ` [Bug fortran/105813] " kargl at gcc dot gnu.org
2022-06-23 21:18 ` anlauf at gcc dot gnu.org
2022-06-23 22:07 ` sgk at troutmask dot apl.washington.edu [this message]
2022-06-24 20:29 ` cvs-commit at gcc dot gnu.org
2022-06-26 20:30 ` anlauf at gcc dot gnu.org
2022-06-30 20:02 ` cvs-commit at gcc dot gnu.org
2022-07-01 17:10 ` cvs-commit at gcc dot gnu.org
2022-07-01 17:24 ` cvs-commit at gcc dot gnu.org
2022-07-01 17:26 ` 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-105813-4-xWBuSDvyvI@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).