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/105747] Scheduler can take a long time on arm-linux sometimes Date: Mon, 19 Feb 2024 13:29:21 +0000 [thread overview] Message-ID: <bug-105747-4-3SQmfvx2kp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105747-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105747 --- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> --- There were some scheduling fixes for GCC 14, possibly time to re-evaluate.
prev parent reply other threads:[~2024-02-19 13:29 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-27 8:49 [Bug c/105747] New: Possible resource hog with -O2 -fno-var-tracking dcb314 at hotmail dot com 2022-05-27 9:14 ` [Bug middle-end/105747] " pinskia at gcc dot gnu.org 2022-05-27 9:22 ` dcb314 at hotmail dot com 2022-05-27 9:31 ` [Bug rtl-optimization/105747] Scheduler can take a long time on arm-linux sometimes pinskia at gcc dot gnu.org 2022-05-27 11:14 ` rguenth at gcc dot gnu.org 2022-06-07 8:28 ` dcb314 at hotmail dot com 2022-06-07 9:30 ` dcb314 at hotmail dot com 2022-06-11 9:45 ` dcb314 at hotmail dot com 2022-06-11 9:48 ` dcb314 at hotmail dot com 2022-06-12 9:40 ` dcb314 at hotmail dot com 2024-02-19 13:29 ` 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-105747-4-3SQmfvx2kp@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: linkBe 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).