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/106911] ICE in gfc_convert_mpz_to_signed, at fortran/simplify.cc:193 Date: Thu, 15 Sep 2022 18:53:16 +0000 [thread overview] Message-ID: <bug-106911-4-womXPvbQ4h@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106911-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106911 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2022-09-15 CC| |anlauf at gcc dot gnu.org --- Comment #2 from anlauf at gcc dot gnu.org --- Confirmed. Potential fix for the ICE: diff --git a/gcc/fortran/simplify.cc b/gcc/fortran/simplify.cc index bc178d54891..c7202ec0b9a 100644 --- a/gcc/fortran/simplify.cc +++ b/gcc/fortran/simplify.cc @@ -3955,6 +3955,9 @@ gfc_simplify_ishftc (gfc_expr *e, gfc_expr *s, gfc_expr *sz) return NULL; gfc_extract_int (sz, &ssize); + + if (ssize > isize || ssize <= 0) + return NULL; } else ssize = isize; However, this would change the issue to an accepts-invalid.
next prev parent reply other threads:[~2022-09-15 18:53 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-12 17:20 [Bug fortran/106911] New: " gscfq@t-online.de 2022-09-12 17:20 ` [Bug fortran/106911] " gscfq@t-online.de 2022-09-15 18:53 ` anlauf at gcc dot gnu.org [this message] 2022-12-10 21:02 ` anlauf at gcc dot gnu.org 2022-12-10 21:14 ` anlauf at gcc dot gnu.org 2022-12-10 21:31 ` cvs-commit at gcc dot gnu.org 2022-12-10 21:33 ` 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-106911-4-womXPvbQ4h@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).