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: Tue, 25 Jul 2023 08:38:44 +0000	[thread overview]
Message-ID: <bug-110587-4-djbPdOEyOa@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

--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
compile-time is back to the first jump caused by r14-2337-g37a231cc7594d1,
thanks Roger.  We still have

 LRA non-specific                   :   3.53 ( 75%)

at -O0 here which Rogers followup patch will improve (but not generally
solve the issue).

At -O1 combine dominates, at -O2 we see other parts of RA being slow:

 integrated RA                      :   7.10 ( 23%) 
 LRA non-specific                   :   1.56 (  5%)
 LRA virtuals elimination           :   0.07 (  0%)
 LRA reload inheritance             :   1.02 (  3%)
 LRA create live ranges             :   0.88 (  3%)
 LRA hard reg assignment            :   8.22 ( 27%)
 LRA coalesce pseudo regs           :   0.00 (  0%)
 LRA rematerialization              :   0.18 (  1%)

Samples: 124K of event 'cycles:u', Event count (approx.): 164730867020          
Overhead       Samples  Command  Shared Object       Symbol                     
  16.60%         20660  cc1      cc1                 [.] find_hard_regno_for_1
  11.90%         14742  cc1      cc1                 [.] bitmap_set_bit
   6.47%          7973  cc1      cc1                 [.] color_allocnos
   3.31%          4023  cc1      cc1                 [.] bitmap_bit_p
   3.07%          3791  cc1      cc1                 [.]
remove_allocno_from_bucket_and_push
   2.77%          3435  cc1      cc1                 [.] assign_hard_reg
   2.54%          3138  cc1      cc1                 [.] ira_build_conflicts

in find_hard_regno_for_1 the loop over live ranges is what's costly, esp.
because it seems the conditionals in the loops depend on (indirect) memory
and that no longer fits nicely into caches.

Maybe regno_allocno_class_array can be shrunk from 'enum reg_class'
(unsigned int) to something smaller.  It looks like this array is a
memory optimization since reg_allocno_class would perform a much sparser
access.

  parent reply	other threads:[~2023-07-25  8:39 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 [this message]
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
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-djbPdOEyOa@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).