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 rtl-optimization/110587] [14 regression] 96% pr28071.c compile time regression since r14-2337-g37a231cc7594d1
Date: Wed, 02 Aug 2023 07:47:34 +0000 [thread overview]
Message-ID: <bug-110587-4-XItrQhhKMg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110587-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110587
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #19 from Richard Biener <rguenth at gcc dot gnu.org> ---
The tester shows the issue is fixed now (we're faster than before the
regression). At -O0 compile-time is still dominated by RA
(r14-2920-g07b7cd70399d22, release checking):
integrated RA : 0.29 ( 32%)
LRA non-specific : 0.15 ( 16%)
TOTAL : 0.91
Samples: 3K of event 'cycles:u', Event count (approx.): 5038659855
Overhead Samples Command Shared Object Symbol
6.15% 233 cc1 cc1 [.] process_alt_operands
4.29% 163 cc1 cc1 [.] process_bb_node_lives
3.72% 142 cc1 cc1 [.] record_reg_classes
3.01% 114 cc1 cc1 [.] mark_ref_dead
2.87% 109 cc1 cc1 [.] constrain_operands
2.71% 114 cc1 cc1 [.]
df_ref_create_structure
2.47% 94 cc1 cc1 [.] ira_setup_alts
next prev parent reply other threads:[~2023-08-02 7:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 9:52 [Bug middle-end/110587] New: 96% pr28071.c compile time regression betwen g:8377cf1bf41a0a9d9d49de807b2341f0bf5d30cf and g:3a61ca1b9256535e1bfb19b2d46cde21f3908a5d hubicka at gcc dot gnu.org
2023-07-15 14:11 ` [Bug middle-end/110587] " jamborm at gcc dot gnu.org
2023-07-15 17:20 ` [Bug middle-end/110587] [14 regression] 96% pr28071.c compile time regression since r14-2337-g37a231cc7594d1 pinskia at gcc dot gnu.org
2023-07-15 17:21 ` [Bug rtl-optimization/110587] " pinskia at gcc dot gnu.org
2023-07-17 6:27 ` crazylht at gmail dot com
2023-07-17 6:28 ` crazylht at gmail dot com
2023-07-17 8:56 ` jamborm at gcc dot gnu.org
2023-07-17 9:13 ` rguenth at gcc dot gnu.org
2023-07-17 10:52 ` jamborm at gcc dot gnu.org
2023-07-17 11:09 ` rguenth at gcc dot gnu.org
2023-07-17 11:26 ` roger at nextmovesoftware dot com
2023-07-17 11:42 ` rguenth at gcc dot gnu.org
2023-07-17 16:04 ` roger at nextmovesoftware dot com
2023-07-18 8:25 ` rguenth at gcc dot gnu.org
2023-07-22 20:55 ` cvs-commit at gcc dot gnu.org
2023-07-25 8:38 ` rguenth at gcc dot gnu.org
2023-07-25 8:44 ` roger at nextmovesoftware dot com
2023-07-27 18:28 ` roger at nextmovesoftware dot com
2023-07-28 8:40 ` cvs-commit at gcc dot gnu.org
2023-08-02 7:04 ` cvs-commit at gcc dot gnu.org
2023-08-02 7:47 ` rguenth at gcc dot gnu.org [this message]
2023-08-02 9:11 ` ubizjak at gmail dot com
2023-08-02 9:45 ` rguenth at gcc dot gnu.org
2023-08-09 6:48 ` 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-110587-4-XItrQhhKMg@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).