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/111600] [14 Regression] RISC-V bootstrap time regression
Date: Wed, 04 Oct 2023 06:46:50 +0000 [thread overview]
Message-ID: <bug-111600-4-kyfbYYydGQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111600-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600
--- Comment #15 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think despite looking at the total size of the files it would be nice to see
if some of the large functions take a lot of compile-time (and where) and see
whether some more intelligent code emission helps. Like I pointed out stuff
like
insn_code
maybe_code_for_pred_indexed_load (int arg0, machine_mode arg1, machine_mode
arg2)
{
if (arg0 == 84
&& arg1 == E_RVVMF8x2QImode
&& arg2 == E_RVVMF8QImode)
return CODE_FOR_pred_indexed_oloadrvvmf8x2qirvvmf8qi;
if (arg0 == 85
&& arg1 == E_RVVMF8x2QImode
&& arg2 == E_RVVMF8QImode)
return CODE_FOR_pred_indexed_uloadrvvmf8x2qirvvmf8qi;
if (arg0 == 84
&& arg1 == E_RVVMF8x3QImode
&& arg2 == E_RVVMF8QImode)
return CODE_FOR_pred_indexed_oloadrvvmf8x3qirvvmf8qi;
if (arg0 == 85
&& arg1 == E_RVVMF8x3QImode
&& arg2 == E_RVVMF8QImode)
...
that requires GCC to do a lot of jump threading to arrive at essentially
nested switches or a fancy lookup table (combining all args) to get this
to a point where it also behaves in a sane way at runtime (the above at -O0
would also execute very slowly).
next prev parent reply other threads:[~2023-10-04 6:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 13:35 [Bug target/111600] New: [14.0 regression] " schwab@linux-m68k.org
2023-09-26 17:41 ` [Bug target/111600] " pinskia at gcc dot gnu.org
2023-09-27 7:36 ` [Bug target/111600] [14 Regression] " rguenth at gcc dot gnu.org
2023-09-27 7:47 ` schwab@linux-m68k.org
2023-09-27 7:50 ` schwab@linux-m68k.org
2023-09-27 8:00 ` rguenth at gcc dot gnu.org
2023-09-27 13:36 ` schwab@linux-m68k.org
2023-09-27 17:50 ` palmer at gcc dot gnu.org
2023-09-27 18:22 ` schwab@linux-m68k.org
2023-09-28 8:06 ` schwab@linux-m68k.org
2023-09-28 9:47 ` rguenth at gcc dot gnu.org
2023-09-28 13:14 ` cvs-commit at gcc dot gnu.org
2023-10-02 15:03 ` rdapp at gcc dot gnu.org
2023-10-02 15:28 ` kito at gcc dot gnu.org
2023-10-03 15:26 ` kito at gcc dot gnu.org
2023-10-04 6:46 ` rguenth at gcc dot gnu.org [this message]
2023-10-04 8:17 ` rdapp at gcc dot gnu.org
2023-10-04 9:07 ` rguenther at suse dot de
2023-10-04 12:50 ` rdapp at gcc dot gnu.org
2023-10-04 13:13 ` rguenth at gcc dot gnu.org
2023-10-04 13:21 ` rdapp at gcc dot gnu.org
2023-10-04 13:56 ` rguenth at gcc dot gnu.org
2023-10-04 14:38 ` rdapp at gcc dot gnu.org
2023-10-12 11:50 ` rdapp at gcc dot gnu.org
2023-10-13 1:39 ` juzhe.zhong at rivai dot ai
2023-10-13 7:28 ` rdapp at gcc dot gnu.org
2023-10-13 8:01 ` rdapp at gcc dot gnu.org
2023-10-13 8:04 ` rguenther at suse dot de
2023-10-31 12:35 ` cvs-commit at gcc dot gnu.org
2023-11-01 2:24 ` juzhe.zhong at rivai dot ai
2023-11-02 9:31 ` rdapp at gcc dot gnu.org
2023-11-06 18:15 ` schwab@linux-m68k.org
2023-11-06 22:07 ` juzhe.zhong at rivai dot ai
2024-03-04 4:31 ` law at gcc dot gnu.org
2024-04-30 8:26 ` [Bug target/111600] [14/15 " cvs-commit at gcc dot gnu.org
2024-05-07 7:42 ` 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-111600-4-kyfbYYydGQ@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).