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/109192] [13 Regression] timeout with -O3 since r13-5579 Date: Mon, 20 Mar 2023 20:20:39 +0000 [thread overview] Message-ID: <bug-109192-4-JWvo3rsoBU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109192-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109192 --- Comment #7 from Andrew Macleod <amacleod at redhat dot com> --- Created attachment 54716 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54716&action=edit proposed patch This is due to the latter part of the specified patch. We normally terminate outgoing range calculations once the LHS has reverted to VARYING as we won't learn anything new. The original patch modified this such that if there was a relation present, we continued calculating as the relation may provide new information, as per the original PR. The problem exposed in this PR is that the presence of a relation doesn't mean that relation can actually affect the range. This PR shows many relations, none of which are relevant, and with the quadratic nature of the path query, it makes things quite bad. The attached patch is in testing. It adds a check to determine if the relation can affect the outgoing range or not by checking if the operands are used in the calculation or not. If they are not in the definition chain, they can have no impact, and we stop the attempt.
next prev parent reply other threads:[~2023-03-20 20:20 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-19 10:20 [Bug c/109192] New: timeout with -g -O3 -fno-var-tracking ? dcb314 at hotmail dot com 2023-03-19 16:56 ` [Bug middle-end/109192] timeout with " dcb314 at hotmail dot com 2023-03-19 17:18 ` dcb314 at hotmail dot com 2023-03-19 17:18 ` dcb314 at hotmail dot com 2023-03-19 19:11 ` [Bug tree-optimization/109192] [13 Regression] timeout with -O3 -fno-var-tracking since r13-5579 pinskia at gcc dot gnu.org 2023-03-20 10:25 ` [Bug tree-optimization/109192] [13 Regression] timeout with -O3 " rguenth at gcc dot gnu.org 2023-03-20 10:35 ` rguenth at gcc dot gnu.org 2023-03-20 20:20 ` amacleod at redhat dot com [this message] 2023-03-21 10:33 ` rguenth at gcc dot gnu.org 2023-03-21 14:15 ` cvs-commit at gcc dot gnu.org 2023-03-21 14:15 ` amacleod at redhat dot com 2023-03-21 14:20 ` rguenth at gcc dot gnu.org 2023-03-28 7:52 ` chenglulu at loongson dot cn 2023-03-28 8:07 ` chenglulu at loongson dot cn 2023-03-28 13:22 ` amacleod at redhat dot com 2023-03-30 1:04 ` chenglulu at loongson dot cn
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-109192-4-JWvo3rsoBU@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).