public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104038] ranger infinite loop on a PHI statement while building Clang
Date: Tue, 18 Jan 2022 15:31:39 +0000 [thread overview]
Message-ID: <bug-104038-4-BJ8mzHJCcq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104038-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104038
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>:
https://gcc.gnu.org/g:254ada46ae0f21bd6f40314214f969f368328e22
commit r12-6678-g254ada46ae0f21bd6f40314214f969f368328e22
Author: Andrew MacLeod <amacleod@redhat.com>
Date: Mon Jan 17 12:03:18 2022 -0500
Limit the number of relations registered per basic block.
In pathological cases, the number of transitive relations being added is
potentially quadratic. Lookups for relations in a block is linear in
nature, so simply limit the number of relations to some reasonable number.
PR tree-optimization/104038
* doc/invoke.texi (relation-block-limit): New.
* params.opt (relation-block-limit): New.
* value-relation.cc (dom_oracle::register_relation): Check for NULL
record before invoking transitive registery.
(dom_oracle::set_one_relation): Check limit before creating record.
(dom_oracle::register_transitives): Stop when no record created.
* value-relation.h (relation_chain_head::m_num_relations): New.
next prev parent reply other threads:[~2022-01-18 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 21:58 [Bug tree-optimization/104038] New: ranger infinite loop on a PHI statement msebor at gcc dot gnu.org
2022-01-14 22:00 ` [Bug tree-optimization/104038] " msebor at gcc dot gnu.org
2022-01-14 22:02 ` msebor at gcc dot gnu.org
2022-01-14 22:07 ` msebor at gcc dot gnu.org
2022-01-14 22:17 ` msebor at gcc dot gnu.org
2022-01-15 0:13 ` pinskia at gcc dot gnu.org
2022-01-15 0:13 ` pinskia at gcc dot gnu.org
2022-01-16 0:03 ` [Bug tree-optimization/104038] ranger infinite loop on a PHI statement while building Clang msebor at gcc dot gnu.org
2022-01-16 15:57 ` amacleod at redhat dot com
2022-01-18 15:31 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-18 15:32 ` amacleod at redhat 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-104038-4-BJ8mzHJCcq@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: link
Be 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).