public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kito 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: Tue, 03 Oct 2023 15:26:07 +0000 [thread overview]
Message-ID: <bug-111600-4-Py2EX35gc9@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 #14 from Kito Cheng <kito at gcc dot gnu.org> ---
Some info for generated files:
---------------------------------------------------------------------------------
File blank comment code
---------------------------------------------------------------------------------
insn-output.cc 3532 35029 1631721
insn-emit.cc 37288 40240 1161790
insn-recog.cc 44203 23 428130
insn-attrtab.cc 1014 30 169934
gimple-match-2.cc 77 2 49303
gimple-match-9.cc 29 2 33073
insn-extract.cc 241 8 28934
gimple-match-1.cc 105 2 25578
gimple-match-8.cc 114 2 24348
options.cc 325 1 24175
insn-opinit.cc 12 6 20156
generic-match-9.cc 55 2 19080
gimple-match-3.cc 98 2 17433
gimple-match-7.cc 108 2 17105
gimple-match-10.cc 129 2 16888
gimple-match-6.cc 115 2 16836
gimple-match-4.cc 97 2 16830
gimple-match-5.cc 99 2 16377
generic-match-3.cc 57 2 16138
options-save.cc 1037 19 15121
generic-match-4.cc 70 2 14095
gtype-desc.cc 679 30 12597
insn-automata.cc 73 11 11735
generic-match-2.cc 60 2 11543
generic-match-1.cc 56 2 11504
generic-match-7.cc 66 2 10238
generic-match-5.cc 71 2 10231
generic-match-10.cc 66 2 9860
generic-match-6.cc 61 2 9853
generic-match-8.cc 53 2 9651
insn-modes.cc 750 410 7655
min-insn-modes.cc 9 2 2280
gengtype-lex.cc 398 424 2126
insn-preds.cc 146 32 1515
insn-dfatab.cc 31 3 1230
insn-latencytab.cc 26 3 1142
gcc-ranlib.cc 55 49 196
insn-enums.cc 6 2 173
insn-peep.cc 7 2 34
cc1-checksum.cc 0 0 3
cc1plus-checksum.cc 0 0 3
next prev parent reply other threads:[~2023-10-03 15:26 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 [this message]
2023-10-04 6:46 ` rguenth at gcc dot gnu.org
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-Py2EX35gc9@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).