public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/103691] [12 Regression] ICE in get_array_ctor_element_at_index, at fold-const.c:13314 since r12-4694-gcb153222404e2e14 Date: Tue, 14 Dec 2021 15:43:42 +0000 [thread overview] Message-ID: <bug-103691-4-bFXD6qCyQ9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103691-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103691 --- Comment #2 from Andrew Macleod <amacleod at redhat dot com> --- Its triggering an assert in the gimple folder when trying to process: # DEBUG D.4293 => &a[0] The constructor shows: static real(kind=4) a[0] = {[0 ... -1]=2.0e+0}; is that a range of 0 to -1? its triggering an assert in line 13314 of fold_const: gcc_checking_assert (wi::le_p (index, max_index, index_sgn)); it looks to be because max_index is less than index? The referenced change causes this because it now calls gimple_fold on all stmts instead of just ranger specific ones. I presume we are suppose to call fold on debug stmts too?
next prev parent reply other threads:[~2021-12-14 15:43 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-13 19:51 [Bug fortran/103691] New: [12 Regression] ICE in get_array_ctor_element_at_index, at fold-const.c:13314 gscfq@t-online.de 2021-12-14 10:05 ` [Bug fortran/103691] [12 Regression] ICE in get_array_ctor_element_at_index, at fold-const.c:13314 since r12-4694-gcb153222404e2e14 marxin at gcc dot gnu.org 2021-12-14 15:43 ` amacleod at redhat dot com [this message] 2022-01-04 11:07 ` rguenth at gcc dot gnu.org 2022-01-04 11:32 ` jakub at gcc dot gnu.org 2022-01-04 12:26 ` rguenth at gcc dot gnu.org 2022-01-04 12:28 ` jakub at gcc dot gnu.org 2022-01-05 9:46 ` cvs-commit at gcc dot gnu.org 2022-01-05 9:49 ` jakub at gcc dot gnu.org 2022-03-24 15:23 ` jakub at gcc dot gnu.org 2022-03-25 10:23 ` cvs-commit at gcc dot gnu.org 2022-03-25 10:23 ` jakub 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-103691-4-bFXD6qCyQ9@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: linkBe 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).