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 rtl-optimization/111554] [12/13/14 regression] Timeout with with "-O3 -fno-dse -fno-inline -fno-store-merging -fno-toplevel-reorder -fno-tree-dce -fno-tree-dse" since r12-2097-g9f34b780b0461e
Date: Mon, 23 Oct 2023 09:54:25 +0000 [thread overview]
Message-ID: <bug-111554-4-yuKf4pvb7R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111554-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111554
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mkuvyrkov at gcc dot gnu.org
Status|UNCONFIRMED |NEW
Last reconfirmed| |2023-10-23
Ever confirmed|0 |1
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Most definitely something like
/* Find the dep_link with consumer CON in producer's forw_deps. */
FOR_EACH_DEP (pro, pro_list_type, sd_it, dep)
if (DEP_CON (dep) == con)
{
found_p = true;
break;
}
is quite bad engineering. The LIM change probably just triggered this to be
observable.
git puts the blame on Maxim, but he might just have refactored the code. Still
he's the remaining scheduler expert, so ... ;)
next prev parent reply other threads:[~2023-10-23 9:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 16:57 [Bug c/111554] New: Timeout with with "-O3 -fno-dse -fno-inline -fno-store-merging -fno-toplevel-reorder -fno-tree-dce -fno-tree-dse" 19373742 at buaa dot edu.cn
2023-09-23 16:57 ` [Bug c/111554] " 19373742 at buaa dot edu.cn
2023-09-23 17:02 ` [Bug rtl-optimization/111554] " pinskia at gcc dot gnu.org
2023-10-22 23:46 ` [Bug rtl-optimization/111554] [12/13/14 regression] " sjames at gcc dot gnu.org
2023-10-22 23:55 ` pinskia at gcc dot gnu.org
2023-10-23 3:27 ` [Bug rtl-optimization/111554] [12/13/14 regression] Timeout with with "-O3 -fno-dse -fno-inline -fno-store-merging -fno-toplevel-reorder -fno-tree-dce -fno-tree-dse" since r12-2097-g9f34b780b0461e sjames at gcc dot gnu.org
2023-10-23 3:48 ` pinskia at gcc dot gnu.org
2023-10-23 3:53 ` pinskia at gcc dot gnu.org
2023-10-23 4:52 ` pinskia at gcc dot gnu.org
2023-10-23 5:01 ` pinskia at gcc dot gnu.org
2023-10-23 9:54 ` rguenth at gcc dot gnu.org [this message]
2023-10-30 13:47 ` mkuvyrkov at gcc dot gnu.org
2023-11-19 8:47 ` mkuvyrkov at gcc dot gnu.org
2023-11-20 8:18 ` rguenth at gcc dot gnu.org
2023-11-20 12:09 ` mkuvyrkov at gcc dot gnu.org
2024-01-17 7:48 ` cvs-commit at gcc dot gnu.org
2024-01-17 8:42 ` [Bug rtl-optimization/111554] [12/13 " rguenth at gcc dot gnu.org
2024-01-17 10:18 ` mkuvyrkov at gcc dot gnu.org
2024-01-17 12:35 ` 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-111554-4-yuKf4pvb7R@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).