public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96729] [11 Regression] slow compile with `-g -O3` since r11-39-gf9e1ea10e657af9f
Date: Tue, 25 Aug 2020 19:12:49 +0000 [thread overview]
Message-ID: <bug-96729-4-gRTzpGvkFO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96729-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96729
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
> Samples: 7K of event 'cycles:u', Event count (approx.): 7668407627
>
> Overhead Command Shared Object Symbol
>
> 26.63% cc1 cc1 [.] dwarf2out_next_real_insn
> 9.81% cc1 cc1 [.]
> is_a_helper<rtx_insn*>::test<rtx_def>
>
> guess there's some quadraticness here, walking the insn stream more times
> than necessary.
For the thousands of consecutive NOTE_INSN_VAR_LOCATION notes case
dwarf2out_var_location has a cache that avoids calling dwarf2out_next_real_insn
for each and thus the quadratic behavior.
Unfortunately the addition of NOTE_INSN_BEGIN_STMT and/or
NOTE_INSN_INLINE_ENTRY broke how this cache works, because
dwarf2out_var_location isn't called in those cases.
next prev parent reply other threads:[~2020-08-25 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 2:01 [Bug c/96729] New: hang on x86_64-linux-gnu with `-g -O3` cnsun at uwaterloo dot ca
2020-08-24 8:16 ` [Bug tree-optimization/96729] [11 Regression] hang on x86_64-linux-gnu with `-g -O3` since r11-39-gf9e1ea10e657af9f marxin at gcc dot gnu.org
2020-08-25 11:19 ` rguenth at gcc dot gnu.org
2020-08-25 12:37 ` rguenth at gcc dot gnu.org
2020-08-25 12:41 ` rguenth at gcc dot gnu.org
2020-08-25 19:12 ` jakub at gcc dot gnu.org [this message]
2020-08-25 19:59 ` [Bug debug/96729] [11 Regression] slow compile " jakub at gcc dot gnu.org
2020-08-26 8:11 ` rguenth at gcc dot gnu.org
2020-08-26 8:31 ` cvs-commit at gcc dot gnu.org
2020-09-11 7:47 ` cvs-commit at gcc dot gnu.org
2020-09-16 19:23 ` cvs-commit at gcc dot gnu.org
2020-09-17 17:59 ` jakub 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-96729-4-gRTzpGvkFO@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).