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/104848] ICE in simplify_intrinsic_op, at fortran/expr.cc:1305 Date: Wed, 09 Mar 2022 19:54:57 +0000 [thread overview] Message-ID: <bug-104848-4-u6yqNZTO7a@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104848-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104848 --- Comment #3 from anlauf at gcc dot gnu.org --- Workaround: using -fno-range-check produces an error where appropriate. Debugging suggests a potential fix for the ICE (needs testing): diff --git a/gcc/fortran/expr.cc b/gcc/fortran/expr.cc index c9c0ba4cc2e..cfafe10f727 100644 --- a/gcc/fortran/expr.cc +++ b/gcc/fortran/expr.cc @@ -1293,7 +1293,7 @@ simplify_intrinsic_op (gfc_expr *p, int type) gfc_internal_error ("simplify_intrinsic_op(): Bad operator"); } - if (result == NULL) + if (result == NULL || result->expr_type == EXPR_UNKNOWN) { gfc_free_expr (op1); gfc_free_expr (op2); But that may be just a band-aid.
next prev parent reply other threads:[~2022-03-09 19:54 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-08 20:00 [Bug fortran/104848] New: " gscfq@t-online.de 2022-03-09 19:34 ` [Bug fortran/104848] " anlauf at gcc dot gnu.org 2022-03-09 19:36 ` anlauf at gcc dot gnu.org 2022-03-09 19:54 ` anlauf at gcc dot gnu.org [this message] 2022-03-09 20:17 ` anlauf at gcc dot gnu.org 2022-10-19 19:18 ` anlauf at gcc dot gnu.org 2024-03-22 21:26 ` anlauf at gcc dot gnu.org 2024-03-22 21:30 ` anlauf at gcc dot gnu.org 2024-04-02 17:49 ` 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-104848-4-u6yqNZTO7a@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).