public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/111303] ICE: in type, at value-range.h:869 Date: Wed, 06 Sep 2023 12:36:21 +0000 [thread overview] Message-ID: <bug-111303-4-E6wLMT1cJa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111303-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111303 --- Comment #3 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> --- In the pattern of match.pd, there is: && range_op_handler (PLUS_EXPR).overflow_free_p (vr0, vr1) && get_range_query (cfun)->range_of_expr (vr3, @3) /* "X+C" and "X" are not of opposite sign. */ && (TYPE_UNSIGNED (type) || (vr0.nonnegative_p () && vr3.nonnegative_p ()) || (vr0.nonpositive_p () && vr3.nonpositive_p ()))) For this case, "vr3" is "undefined_p", then "vr3.nonnegative_p ()" trige ICE. Checking "!vr3.undefine_p ()" would be a safe fix for this ICE.
next prev parent reply other threads:[~2023-09-06 12:36 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-06 8:24 [Bug c/111303] New: " shaohua.li at inf dot ethz.ch 2023-09-06 9:21 ` [Bug c/111303] " shaohua.li at inf dot ethz.ch 2023-09-06 11:12 ` guojiufu at gcc dot gnu.org 2023-09-06 11:13 ` guojiufu at gcc dot gnu.org 2023-09-06 12:36 ` guojiufu at gcc dot gnu.org [this message] 2023-09-06 12:47 ` guojiufu at gcc dot gnu.org 2023-09-06 22:52 ` [Bug tree-optimization/111303] [14 Regression] " pinskia at gcc dot gnu.org 2023-09-09 16:03 ` pinskia at gcc dot gnu.org 2023-09-09 16:04 ` pinskia at gcc dot gnu.org 2023-09-13 1:32 ` cvs-commit at gcc dot gnu.org 2023-09-18 2:19 ` cvs-commit at gcc dot gnu.org 2023-09-18 2:31 ` guojiufu at gcc dot gnu.org 2023-09-18 2:38 ` guojiufu 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-111303-4-E6wLMT1cJa@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).