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 middle-end/102948] [12 Regression] 60% build time regression on gamess in range 2fc2e3917f9c8fd94f5d101477971d16c483ef88...c16f21c7cf97ce48967e42d3b5d22ea169a9c2c8
Date: Wed, 27 Oct 2021 08:00:06 +0000 [thread overview]
Message-ID: <bug-102948-4-dCESyFmRmz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102948-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102948
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
96c82a16b2076891a9974d0f0e96a0b85fbc2df4 is bad
runspec finished at Wed Oct 27 09:28:33 2021; 248 total seconds elapsed
278.22user 6.12system 4:06.58elapsed 115%CPU (0avgtext+0avgdata
838228maxresident)k
0inputs+152088outputs (0major+1419291minor)pagefaults 0swaps
af31cab04770f7a1a1da069415ab62ca2ef54fc4 is good (moderately)
runspec finished at Wed Oct 27 09:34:40 2021; 226 total seconds elapsed
256.97user 6.09system 3:45.05elapsed 116%CPU (0avgtext+0avgdata
837948maxresident)k
0inputs+148880outputs (0major+1401504minor)pagefaults 0swaps
0d04fe49239d91787850036599164788f1c87785 is good
runspec finished at Wed Oct 27 09:39:11 2021; 220 total seconds elapsed
250.27user 6.17system 3:38.41elapsed 117%CPU (0avgtext+0avgdata
837744maxresident)k
0inputs+148896outputs (0major+1396728minor)pagefaults 0swaps
text data bss dec hex filename
9949090 65752 659317536 669332378 27e5339a
f2e5d2717d9e249edc5e0d45e49e4f9ef81fc694 is good
runspec finished at Wed Oct 27 09:44:40 2021; 224 total seconds elapsed
254.50user 6.21system 3:42.45elapsed 117%CPU (0avgtext+0avgdata
837940maxresident)k
0inputs+148608outputs (0major+1401035minor)pagefaults 0swaps
text data bss dec hex filename
9949090 65752 659317536 669332378 27e5339a
9fcb8ec60302f5f110f94a885b618993c28d18d3 is bad
runspec finished at Wed Oct 27 09:50:42 2021; 252 total seconds elapsed
282.56user 6.22system 4:10.48elapsed 115%CPU (0avgtext+0avgdata
838672maxresident)k
0inputs+152104outputs (0major+1413973minor)pagefaults 0swaps
text data bss dec hex filename
10767019 65760 659317536 670150315 27f1aeab
bisected to [31855ba6b16cd138d7484076a08cd40d609654b8] Add emulated gather
capability to the vectorizer
runspec finished at Wed Oct 27 09:57:25 2021; 247 total seconds elapsed
277.33user 6.05system 4:05.74elapsed 115%CPU (0avgtext+0avgdata
838248maxresident)k
0inputs+151808outputs (0major+1421290minor)pagefaults 0swaps
text data bss dec hex filename
10767019 65760 659317536 670150315 27f1aeab
next prev parent reply other threads:[~2021-10-27 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:53 [Bug middle-end/102948] New: " hubicka at gcc dot gnu.org
2021-10-27 6:48 ` [Bug middle-end/102948] [12 Regression] " rguenth at gcc dot gnu.org
2021-10-27 7:22 ` rguenth at gcc dot gnu.org
2021-10-27 8:00 ` rguenth at gcc dot gnu.org [this message]
2021-11-01 7:28 ` [Bug middle-end/102948] [12 Regression] 60% build time regression on gamess in range g:31855ba6b16cd138d7484076a08cd40d609654b8 marxin at gcc dot gnu.org
2021-11-02 7:08 ` [Bug middle-end/102948] [12 Regression] 60% build time regression on gamess with g:31855ba6b16cd138d7484076a08cd40d609654b8 rguenth at gcc dot gnu.org
2022-01-18 14:39 ` 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-102948-4-dCESyFmRmz@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).