public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "abel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/46522] ICE: in reset_sched_cycles_in_current_ebb, at sel-sched.c:7092 with -O3 -fsel-sched-pipelining -fselective-scheduling2 -funroll-loops Date: Thu, 07 Apr 2011 07:04:00 -0000 [thread overview] Message-ID: <bug-46522-4-THPrICkle0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46522-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46522 --- Comment #6 from Andrey Belevantsev <abel at gcc dot gnu.org> 2011-04-07 07:04:10 UTC --- Author: abel Date: Thu Apr 7 07:04:02 2011 New Revision: 172088 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=172088 Log: Backport from mainline 2011-01-13 Andrey Belevantsev <abel@ispras.ru> PR rtl-optimization/45352 * sel-sched.c: Update copyright years. (reset_sched_cycles_in_current_ebb): Also recheck the DFA state in the advancing loop when we have issued issue_rate insns. Backport from mainline 2010-12-22 Andrey Belevantsev <abel@ispras.ru> PR rtl-optimization/45352 PR rtl-optimization/46521 PR rtl-optimization/46522 * sel-sched.c (reset_sched_cycles_in_current_ebb): Recheck the DFA state on the last iteration of the advancing loop. (sel_sched_region_1): Propagate the rescheduling bit to the next block also for empty blocks. Backport from mainline 2010-11-08 Andrey Belevantsev <abel@ispras.ru> PR rtl-optimization/45352 * sel-sched.c (find_best_expr): Do not set pneed_stall when the variable_issue hook is not implemented. (fill_insns): Remove dead variable stall_iterations. (init_seqno_1): Force EBB start for resetting sched cycles on any successor blocks of the rescheduled region. (sel_sched_region_1): Use bitmap_bit_p instead of bitmap_clear_bit. (reset_sched_cycles_in_current_ebb): Add debug printing. New variable issued_insns. Advance state when we have issued issue_rate insns. Added: branches/gcc-4_5-branch/gcc/testsuite/gcc.dg/pr45352-1.c branches/gcc-4_5-branch/gcc/testsuite/gcc.dg/pr45352-2.c branches/gcc-4_5-branch/gcc/testsuite/gcc.dg/pr45352-3.c branches/gcc-4_5-branch/gcc/testsuite/gcc.dg/pr45352.c branches/gcc-4_5-branch/gcc/testsuite/gcc.dg/pr46521.c branches/gcc-4_5-branch/gcc/testsuite/gcc.dg/pr46522.c branches/gcc-4_5-branch/gcc/testsuite/gcc.target/i386/pr45352-1.c branches/gcc-4_5-branch/gcc/testsuite/gcc.target/i386/pr45352-2.c branches/gcc-4_5-branch/gcc/testsuite/gcc.target/i386/pr45352.c Modified: branches/gcc-4_5-branch/gcc/ChangeLog branches/gcc-4_5-branch/gcc/sel-sched.c branches/gcc-4_5-branch/gcc/testsuite/ChangeLog
prev parent reply other threads:[~2011-04-07 7:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-17 16:14 [Bug rtl-optimization/46522] New: " zsojka at seznam dot cz 2010-11-18 7:31 ` [Bug rtl-optimization/46522] " hjl.tools at gmail dot com 2010-11-18 14:29 ` abel at gcc dot gnu.org 2010-12-21 12:14 ` abel at gcc dot gnu.org 2010-12-22 7:47 ` abel at gcc dot gnu.org 2011-01-13 9:55 ` abel at gcc dot gnu.org 2011-04-07 7:04 ` abel 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-46522-4-THPrICkle0@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).