public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/63384] scheduler loops on endless fence list with -fselective-scheduling2 on x86 Date: Fri, 21 Jun 2024 23:15:06 +0000 [thread overview] Message-ID: <bug-63384-4-BMwGqHzedB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63384-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63384 Andi Kleen <andi-gcc at firstfloor dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #9 from Andi Kleen <andi-gcc at firstfloor dot org> --- Long fixed.
prev parent reply other threads:[~2024-06-21 23:15 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-26 17:33 [Bug rtl-optimization/63384] New: ICE in moveup_expr_chached->sel_bb_head->bb_node with special options andi-gcc at firstfloor dot org 2014-09-28 1:22 ` [Bug rtl-optimization/63384] " andi-gcc at firstfloor dot org 2014-09-28 7:43 ` [Bug rtl-optimization/63384] selective scheduling on x86 takes very long andi-gcc at firstfloor dot org 2014-09-28 17:27 ` [Bug rtl-optimization/63384] scheduler loops on endless fence list with -fselective-scheduling2 on x86 andi-gcc at firstfloor dot org 2024-06-21 23:15 ` andi-gcc at firstfloor dot 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-63384-4-BMwGqHzedB@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).