public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105820] [13 Regression] ICE in invert, at value-range.cc:1971 Date: Thu, 02 Jun 2022 12:18:57 +0000 [thread overview] Message-ID: <bug-105820-4-aBqb7udvVF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105820-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105820 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |13.0 CC| |amacleod at redhat dot com --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- #1 0x0000000001ced6a0 in irange::invert (this=0x7fffffff1f30) at /space/rguenther/src/gcc/gcc/value-range.cc:2166 2166 gcc_checking_assert (!undefined_p () && !varying_p ()); well, invert(undefined) = varying, invert(varying) = undefined - not sure why we assert here. (undefined is another name for 'empty') I've wondered of several places checking for undefined/varying before calling .invert () ...
next prev parent reply other threads:[~2022-06-02 12:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-02 11:10 [Bug tree-optimization/105820] New: " asolokha at gmx dot com 2022-06-02 12:18 ` rguenth at gcc dot gnu.org [this message] 2022-06-02 13:05 ` [Bug tree-optimization/105820] " amacleod at redhat dot com 2022-06-03 5:30 ` aldyh at gcc dot gnu.org 2022-06-16 14:00 ` amacleod at redhat dot com 2022-10-17 11:24 ` asolokha at gmx dot com 2022-10-17 12:14 ` marxin at gcc dot gnu.org 2022-10-17 12:38 ` asolokha at gmx dot com 2022-10-17 12:42 ` marxin at gcc dot gnu.org 2022-10-17 13:41 ` cvs-commit 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-105820-4-aBqb7udvVF@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).