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 with g:31855ba6b16cd138d7484076a08cd40d609654b8
Date: Tue, 18 Jan 2022 14:39:24 +0000 [thread overview]
Message-ID: <bug-102948-4-a5iBrfnyXH@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
The LNT graph shows we're back to good compile-times now. Assuming fixed.
prev parent reply other threads:[~2022-01-18 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:53 [Bug middle-end/102948] New: 60% build time regression on gamess in range 2fc2e3917f9c8fd94f5d101477971d16c483ef88...c16f21c7cf97ce48967e42d3b5d22ea169a9c2c8 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
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 [this message]
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-a5iBrfnyXH@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).