public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101014] [12 Regression] Big compile time hog with -O3 since r12-1268-g9858cd1a6827ee7a
Date: Tue, 15 Jun 2021 06:49:19 +0000 [thread overview]
Message-ID: <bug-101014-4-Xv2ewiW31h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101014-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101014
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
Should be fixed with:
commit ecc5644fa3bc7f37eada2a3e9c627cd1918922e0
Author: Andrew MacLeod <amacleod@redhat.com>
Date: Mon Jun 14 15:33:59 2021 -0400
Limit new value calculations to first order effects.
When utilzing poor values during propagation, we mostly care about values
that
were undefined/processed directly used in calcualting the SSA_NAME being
processed. 2nd level derivations of such poor values rarely affect the
inital calculation. Leave them to when they are directly encountered.
* gimple-range-cache.cc (ranger_cache::ranger_cache): Adjust.
(ranger_cache::enable_new_values): Set to specified value and
return the old value.
(ranger_cache::disable_new_values): Delete.
(ranger_cache::fill_block_cache): Disable non 1st order derived
poor values.
* gimple-range-cache.h (ranger_cache): Adjust prototypes.
* gimple-range.cc (gimple_ranger::range_of_expr): Adjust.
next prev parent reply other threads:[~2021-06-15 6:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 10:58 [Bug tree-optimization/101014] New: " marxin at gcc dot gnu.org
2021-06-10 11:01 ` [Bug tree-optimization/101014] " marxin at gcc dot gnu.org
2021-06-10 11:13 ` marxin at gcc dot gnu.org
2021-06-10 12:23 ` marxin at gcc dot gnu.org
2021-06-10 13:42 ` amacleod at redhat dot com
2021-06-14 20:28 ` amacleod at redhat dot com
2021-06-15 6:49 ` marxin at gcc dot gnu.org [this message]
2021-06-15 13:01 ` amacleod at redhat dot com
2021-06-16 8:38 ` marxin at gcc dot gnu.org
2021-06-16 8:38 ` marxin at gcc dot gnu.org
2021-06-18 21:44 ` cvs-commit at gcc dot gnu.org
2021-06-18 21:46 ` amacleod at redhat dot com
2021-06-21 8:48 ` crazylht at gmail dot com
2021-06-21 9:09 ` aldyh at gcc dot gnu.org
2021-06-21 9:59 ` crazylht at gmail dot com
2021-06-21 10:37 ` rguenth at gcc dot gnu.org
2021-06-22 5:07 ` marxin at gcc dot gnu.org
2021-06-22 5:08 ` marxin at gcc dot gnu.org
2021-06-22 13:55 ` amacleod at redhat dot com
2021-06-22 15:08 ` marxin at gcc dot gnu.org
2021-06-23 14:26 ` cvs-commit at gcc dot gnu.org
2021-06-23 14:31 ` amacleod at redhat dot com
2021-07-14 21:58 ` 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-101014-4-Xv2ewiW31h@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).