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/97359] [11 Regression] ice in logical_combine, at gimple-range-gori.cc:754 Date: Wed, 14 Oct 2020 15:03:50 +0000 [thread overview] Message-ID: <bug-97359-4-1eP1La9fIG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97359-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97359 --- Comment #7 from Andrew Macleod <amacleod at redhat dot com> --- There is no need to cache non-logical operands. Processing a relational such as <,>,<=,>= is a linear process, and therefore we never needed to cache them. && and || is exponential as we have to evaluate op1_true, op1_false, op2_true, and op2_false and the resulting 4 combinations... so each logical operand can trigger 4 lookup calculations.. and when they feed into each other the on-demand lookups become exponential quite quickly.. the cache makes processing them linear as well. Before the next stage 1 opens, I plan to rework the GORI computations to be more efficient on calculating outgoing ranges.
next prev parent reply other threads:[~2020-10-14 15:03 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-09 20:43 [Bug c/97359] New: " dcb314 at hotmail dot com 2020-10-09 20:47 ` [Bug c/97359] " dcb314 at hotmail dot com 2020-10-09 20:54 ` dcb314 at hotmail dot com 2020-10-09 21:34 ` [Bug tree-optimization/97359] [11 Regression] " jakub at gcc dot gnu.org 2020-10-10 6:50 ` aldyh at gcc dot gnu.org 2020-10-10 8:26 ` cvs-commit at gcc dot gnu.org 2020-10-10 8:28 ` aldyh at gcc dot gnu.org 2020-10-14 15:03 ` amacleod at redhat dot com [this message] 2020-11-30 3:11 ` hjl.tools at gmail dot com
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-97359-4-1eP1La9fIG@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).