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 tree-optimization/112843] during GIMPLE pass: bitintlower ICE: SIGSEGV in ranger_cache::range_of_expr (gimple-range-cache.cc:1204) with _BitInt() at -O1 Date: Mon, 04 Dec 2023 18:19:08 +0000 [thread overview] Message-ID: <bug-112843-4-44yxgelKVG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112843-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112843 --- Comment #9 from Andrew Macleod <amacleod at redhat dot com> --- Created attachment 56790 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56790&action=edit auxially patch to avid the trap refining a range is fine... the only issue we are really running into here that is causing the trap is that the "update" on the original LHS DEF is a new stmt which hasnt been added to the IL yet, so ranger is trapping when it asks for the basic block of the def stmt.. It had one before, it expects it to still have one when it looks at the context of the stmt to update the range. Now that said, the update issue is primarily within the cache. if we are updating and the BB isn't set, we could simply just pick up the global value. Patch is attached, and pre-approved if you want to use it.
next prev parent reply other threads:[~2023-12-04 18:19 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-04 11:45 [Bug tree-optimization/112843] New: " zsojka at seznam dot cz 2023-12-04 14:17 ` [Bug tree-optimization/112843] " jakub at gcc dot gnu.org 2023-12-04 14:26 ` rguenth at gcc dot gnu.org 2023-12-04 14:28 ` rguenth at gcc dot gnu.org 2023-12-04 14:32 ` rguenth at gcc dot gnu.org 2023-12-04 16:02 ` amacleod at redhat dot com 2023-12-04 16:13 ` jakub at gcc dot gnu.org 2023-12-04 16:39 ` amacleod at redhat dot com 2023-12-04 16:57 ` jakub at gcc dot gnu.org 2023-12-04 18:19 ` amacleod at redhat dot com [this message] 2023-12-05 8:48 ` cvs-commit at gcc dot gnu.org 2023-12-06 7:28 ` cvs-commit at gcc dot gnu.org 2023-12-06 7:57 ` rguenth 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-112843-4-44yxgelKVG@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).