public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107216] ICE in reduce_binary_aa, at fortran/arith.cc:1427
Date: Wed, 12 Oct 2022 18:48:41 +0000 [thread overview]
Message-ID: <bug-107216-4-ssMEVTfuCZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107216-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107216
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
Ever confirmed|0 |1
Last reconfirmed| |2022-10-12
Status|UNCONFIRMED |NEW
--- Comment #2 from anlauf at gcc dot gnu.org ---
Confirmed.
Strange. Removing any of the typespecs in the array constructors avoids
the issue, i.e.
print *, [real :: 1, 2] * [ 1, (2)]
would just fine.
For z1.f90, I find:
(gdb) p op2->expr_type
$9 = EXPR_FUNCTION
in reduce_binary before we call reduce_binary_aa and everything goes boom.
next prev parent reply other threads:[~2022-10-12 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 16:55 [Bug fortran/107216] New: " gscfq@t-online.de
2022-10-11 16:56 ` [Bug fortran/107216] " gscfq@t-online.de
2022-10-12 18:48 ` anlauf at gcc dot gnu.org [this message]
2022-10-12 19:02 ` anlauf at gcc dot gnu.org
2022-10-17 17:26 ` cvs-commit at gcc dot gnu.org
2022-10-17 17:37 ` 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-107216-4-ssMEVTfuCZ@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).