public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108738] compile-time and memory-hog in mdreorg
Date: Thu, 09 Feb 2023 08:47:47 +0000 [thread overview]
Message-ID: <bug-108738-4-oEmdQoG0pq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108738-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108738
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
A perf report isn't very conclusive, but at least points at STV:
Samples: 3M of event 'cycles:u', Event count (approx.): 4455606089800
Samples Command Shared Object Symbol
2153935 cc1 cc1 [.] bitmap_bit_p
288315 cc1 cc1 [.] (anonymous
namespace)::scalar_chain::analyze_register_chain
145980 cc1 cc1 [.] bitmap_equal_p
85953 cc1 cc1 [.] pop_scope
70985 cc1 cc1 [.] bitmap_ior_into
87675 cc1 cc1 [.] df_chain_create
with -O2 -mno-stv we get to
machine dep reorg : 0.01 ( 0%) 0.00 ( 0%) 0.01 ( 0%)
0 ( 0%)
TOTAL : 202.90 8.46 211.41
1475M
next prev parent reply other threads:[~2023-02-09 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 8:10 [Bug target/108738] New: " rguenth at gcc dot gnu.org
2023-02-09 8:47 ` rguenth at gcc dot gnu.org [this message]
2023-02-09 9:11 ` [Bug target/108738] " rguenth at gcc dot gnu.org
2023-02-09 9:24 ` rguenth at gcc dot gnu.org
2023-02-09 12:48 ` rguenth at gcc dot gnu.org
2023-02-15 7:28 ` cvs-commit at gcc dot gnu.org
2023-02-15 7:28 ` cvs-commit at gcc dot gnu.org
2023-03-02 11:38 ` rguenth at gcc dot gnu.org
2023-03-03 7:31 ` cvs-commit at gcc dot gnu.org
2023-03-03 7:33 ` rguenth 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-108738-4-oEmdQoG0pq@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).