public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92264] [10 Regression] Compile time hog in 521.wrf_r with -Ofast -march=znver2 -g since r276318
Date: Thu, 19 Mar 2020 13:34:22 +0000 [thread overview]
Message-ID: <bug-92264-4-Ni9F9ndDuA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92264-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92264
--- Comment #28 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #25)
> Created attachment 48064 [details]
> more localized caching
>
> Updated and simplified patch. Maybe it does help depending on how we have
> shared locs for multiple values ...
>
> The update is to not bother updating cache values with non-NULL found ones.
So this patch is running for the problematic wrf testcase for more that 2h30m..
next prev parent reply other threads:[~2020-03-19 13:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92264-4@http.gcc.gnu.org/bugzilla/>
2020-03-10 8:09 ` jakub at gcc dot gnu.org
2020-03-17 9:21 ` marxin at gcc dot gnu.org
2020-03-17 9:25 ` marxin at gcc dot gnu.org
2020-03-17 9:46 ` marxin at gcc dot gnu.org
2020-03-17 9:57 ` jakub at gcc dot gnu.org
2020-03-17 11:37 ` marxin at gcc dot gnu.org
2020-03-18 13:25 ` jakub at gcc dot gnu.org
2020-03-18 16:56 ` marxin at gcc dot gnu.org
2020-03-18 20:20 ` marxin at gcc dot gnu.org
2020-03-19 7:48 ` rguenth at gcc dot gnu.org
2020-03-19 7:53 ` marxin at gcc dot gnu.org
2020-03-19 8:00 ` rguenth at gcc dot gnu.org
2020-03-19 8:06 ` rguenth at gcc dot gnu.org
2020-03-19 8:27 ` jakub at gcc dot gnu.org
2020-03-19 8:43 ` marxin at gcc dot gnu.org
2020-03-19 10:38 ` rguenth at gcc dot gnu.org
2020-03-19 10:38 ` rguenth at gcc dot gnu.org
2020-03-19 10:49 ` rguenth at gcc dot gnu.org
2020-03-19 10:50 ` marxin at gcc dot gnu.org
2020-03-19 10:53 ` rguenth at gcc dot gnu.org
2020-03-19 10:54 ` rguenth at gcc dot gnu.org
2020-03-19 13:12 ` jakub at gcc dot gnu.org
2020-03-19 13:34 ` marxin at gcc dot gnu.org [this message]
2020-03-19 14:42 ` jakub at gcc dot gnu.org
2020-03-19 14:57 ` jakub at gcc dot gnu.org
2020-03-20 17:25 ` jakub at gcc dot gnu.org
2020-03-20 18:26 ` jakub at gcc dot gnu.org
2020-03-20 20:49 ` jakub at gcc dot gnu.org
2020-03-23 9:21 ` jakub at gcc dot gnu.org
2020-03-23 9:39 ` marxin at gcc dot gnu.org
2020-03-26 8:16 ` cvs-commit at gcc dot gnu.org
2020-03-26 8:22 ` marxin at gcc dot gnu.org
2020-03-26 8:26 ` jakub at gcc dot gnu.org
2020-04-02 12:31 ` cvs-commit at gcc dot gnu.org
2020-04-02 12:35 ` cvs-commit at gcc dot gnu.org
2020-04-02 14:22 ` marxin at gcc dot gnu.org
2020-04-02 14:28 ` jakub at gcc dot gnu.org
2020-04-02 14:37 ` marxin at gcc dot gnu.org
2020-04-02 14:40 ` jakub at gcc dot gnu.org
2020-04-03 18:47 ` cvs-commit at gcc dot gnu.org
2020-04-03 23:48 ` cvs-commit at gcc dot gnu.org
2020-04-07 23:56 ` 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-92264-4-Ni9F9ndDuA@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).