public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <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: Mon, 21 Jun 2021 09:59:27 +0000	[thread overview]
Message-ID: <bug-101014-4-bbxJXmyPCe@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 #13 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Aldy Hernandez from comment #12)
> (In reply to Hongtao.liu from comment #11)
> > I'm not sure if it's related but compilation of 527.cam4_r still hangs with
> > 
> > gcc version 12.0.0 20210621 (experimental) (GCC) 
> 
> Can you verify after which patch upstream it started hanging?  It may or may
> not be related to this bug.
> 
> Or perhaps, can you check where it hangs?  Is it hanging in the ranger code
> or elsewhere?

After hanging for 36m, with gdb -p pid

(gdb) bt
#0  0x0000000001035810 in irange::varying_compatible_p
(this=this@entry=0x7ffdd7672630)
    at /export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/value-range.h:289
#1  0x000000000102a08b in irange::normalize_kind (this=0x7ffdd7672630)
    at /export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/value-range.h:584
#2  irange::irange_set (this=0x7ffdd7672630, min=<optimized out>,
max=<optimized out>)
    at /export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/value-range.cc:182
#3  0x000000000102922c in range_query::get_tree_range (this=0x2614590
<global_ranges>, r=..., expr=0x148092cd3de0, stmt=0x148092896738)
    at /export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/value-query.cc:212
#4  0x000000000175457e in fold_using_range::range_of_range_op (this=<optimized
out>, r=..., s=0x148092896738, src=...)
    at /export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range.cc:642
#5  0x0000000001757606 in fold_using_range::fold_stmt (this=0x7ffdd76736cf,
r=..., s=0x148092896738, src=..., name=0x1480925eae10)
    at /export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range.cc:577
#6  0x000000000175795d in fold_range (r=..., s=s@entry=0x148092896738,
q=<optimized out>)
    at /export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range.cc:312
#7  0x000000000175a5d3 in ranger_cache::range_of_def (this=0x7ffdd7687950,
r=..., name=0x1480925eae10, bb=0x0)
    at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range-cache.cc:842
#8  0x000000000175a690 in ranger_cache::entry_range (this=0x7ffdd7687950,
r=..., name=0x1480925eae10, bb=0x148092bffbc8)
    at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range-cache.cc:866
#9  0x000000000175a796 in ranger_cache::range_of_expr (this=<optimized out>,
r=..., name=<optimized out>, stmt=<optimized out>)
    at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range-cache.cc:914
#10 0x000000000175faaa in gori_compute::compute_operand1_range
(this=0x7ffdd76879d0, r=..., stmt=0x14809245bb40, lhs=..., 
    name=0x1480932cf9d8, src=...) at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range-gori.cc:877
#11 0x000000000176083a in gori_compute::compute_operand_range (src=...,
name=0x1480932cf9d8, lhs=..., stmt=0x14809245bb40, r=..., 
    this=0x7ffdd76879d0) at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range-gori.cc:620
#12 gori_compute::outgoing_edge_range_p (this=this@entry=0x7ffdd76879d0, r=...,
e=e@entry=0x14809234a750, name=name@entry=0x1480932cf9d8, 
    q=...) at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range-gori.cc:1044
#13 0x000000000175ae00 in ranger_cache::propagate_cache (this=0x7ffdd7687950,
name=0x1480932cf9d8)
    at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range-cache.cc:1027
#14 0x000000000175b4e7 in ranger_cache::fill_block_cache (this=0x7ffdd7687950,
name=0x1480932cf9d8, bb=<optimized out>, 
    def_bb=0x1480933e5ea0) at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range-cache.cc:1238
#15 0x000000000175b980 in ranger_cache::block_range (this=0x7ffdd7687950,
r=..., bb=0x148092c4e680, name=0x1480932cf9d8, 
    calc=<optimized out>) at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range-cache.cc:971
#16 0x0000000001753a92 in gimple_ranger::range_on_entry (this=0x7ffdd7687940,
r=..., bb=0x148092c4e680, name=0x1480932cf9d8)
    at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range.cc:1203
#17 0x0000000001757cef in gimple_ranger::range_of_expr (this=<optimized out>,
r=..., expr=0x1480932cf9d8, stmt=<optimized out>)
    at
/export/users2/liuhongt/gcc/gnu-toolchain/master/gcc/gimple-range.cc:1186

> 
> Thanks.

  parent reply	other threads:[~2021-06-21  9:59 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
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 [this message]
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-bbxJXmyPCe@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).