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: Sun, 28 Sep 2014 17:27:00 -0000 [thread overview] Message-ID: <bug-63384-4-fTnczlzl4P@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 --- Comment #4 from Andi Kleen <andi-gcc at firstfloor dot org> --- It loops forever in this loop in sel_sched_region_2 while (fences) { int min_seqno, max_seqno; ilist_t scheduled_insns = NULL; ilist_t *scheduled_insns_tailp = &scheduled_insns; find_min_max_seqno (fences, &min_seqno, &max_seqno); schedule_on_fences (fences, max_seqno, &scheduled_insns_tailp); fences = calculate_new_fences (fences, orig_max_seqno, &max_time); highest_seqno_in_use = update_seqnos_and_stage (min_seqno, max_seqno, highest_seqno_in_use, &scheduled_insns); } because calculate_new_fences always comes up with a list which is the same as before. In move_fence_to_fences it always goes into the else f = flist_lookup (FLIST_TAIL_HEAD (new_fences), FENCE_INSN (FLIST_FENCE (old_fences))); if (f) { merge_fences (f, old->insn, old->state, old->dc, old->tc, old->last_scheduled_insn, old->executing_insns, old->ready_ticks, old->ready_ticks_size, old->sched_next, old->cycle, old->issue_more, old->after_stall_p); } else { _list_add (tailp); FLIST_TAIL_TAILP (new_fences) = &FLIST_NEXT (*tailp); So something is going wrong in flist_lookup.
next prev parent reply other threads:[~2014-09-28 17:27 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 ` andi-gcc at firstfloor dot org [this message] 2024-06-21 23:15 ` [Bug rtl-optimization/63384] scheduler loops on endless fence list with -fselective-scheduling2 on x86 andi-gcc at firstfloor dot 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-63384-4-fTnczlzl4P@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).