public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/56023] [4.6 Regression]: [alpha] -fcompare-debug failure due to sched1 pass Date: Sat, 19 Jan 2013 10:18:00 -0000 [thread overview] Message-ID: <bug-56023-4-59wd4ueh14@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56023-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56023 --- Comment #8 from Uros Bizjak <ubizjak at gmail dot com> 2013-01-19 10:17:43 UTC --- The scheduler passes block boundary here and schedules insns from the next block. This is the difference to the compilation w/o -g and to gcc-4_7 branch. ;; ====================================================== ;; -- basic block 10 from 99 to 102 -- before reload ;; ====================================================== ;; --------------- forward dependences: ------------ ;; --- Region Dependences --- b 10 bb 5 ;; insn code bb dep prio cost reservation ;; ---- ---- -- --- ---- ---- ----------- ;; 99 -1 10 0 0 0 nothing : 43 100 ;; 100 -1 10 1 0 0 nothing : ;; 102 184 10 0 2 2 (ev4_ib1+ev4_bbox),ev4_bbox : 44 ;; --- Region Dependences --- b 4 bb 6 ;; insn code bb dep prio cost reservation ;; ---- ---- -- --- ---- ---- ----------- ;; 29 52 4 0 9 2 (ev4_ib0+ev4_ebox) : 44 30 ;; 30 159 4 1 7 2 (ev4_ib0+ev4_ebox) : 44 31 ;; 31 159 4 1 5 2 (ev4_ib0+ev4_ebox) : 44 39 ;; 35 159 4 0 5 2 (ev4_ib0+ev4_ebox) : 44 39 ;; 37 NOTE_INSN_DELETED ;; 38 NOTE_INSN_DELETED ;; 39 41 4 2 3 2 (ev4_ib0+ev4_ebox) : 44 ;; 40 NOTE_INSN_DELETED ;; 41 3 4 0 2 2 (ev4_ib0+ev4_ebox) : 44 ;; 42 NOTE_INSN_DELETED ;; 43 3 4 0 2 2 (ev4_ib0+ev4_ebox) : 44 ;; 44 184 4 8 2 2 (ev4_ib1+ev4_bbox),ev4_bbox : ;; dependencies resolved: insn 99 ;; tick updated: insn 99 into ready ;; dependencies resolved: insn 102 ;; Ready-->Q: insn 102: queued for 2 cycles. ;; tick updated: insn 102 into queue with cost=2 ;; dependencies resolved: insn 29/b6 ;; Ready-->Q: insn 29/b6: queued for 2 cycles. ;; tick updated: insn 29/b6 into queue with cost=2 ;; dependencies resolved: insn 35/b6 ;; Ready-->Q: insn 35/b6: queued for 2 cycles. ;; tick updated: insn 35/b6 into queue with cost=2 ;; dependencies resolved: insn 41/b6 ;; Ready-->Q: insn 41/b6: queued for 2 cycles. ;; tick updated: insn 41/b6 into queue with cost=2 ;; dependencies resolved: insn 43/b6 ;; Ready-->Q: insn 43/b6: queued for 2 cycles. ;; tick updated: insn 43/b6 into queue with cost=2 ;; Advanced a state. ;; ...
next prev parent reply other threads:[~2013-01-19 10:18 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-17 22:03 [Bug rtl-optimization/56023] New: " ubizjak at gmail dot com 2013-01-17 22:09 ` [Bug rtl-optimization/56023] " ubizjak at gmail dot com 2013-01-17 22:11 ` ubizjak at gmail dot com 2013-01-17 23:00 ` ubizjak at gmail dot com 2013-01-18 10:19 ` rguenth at gcc dot gnu.org 2013-01-18 17:05 ` ubizjak at gmail dot com 2013-01-18 17:38 ` ubizjak at gmail dot com 2013-01-18 17:49 ` ubizjak at gmail dot com 2013-01-19 10:06 ` ubizjak at gmail dot com 2013-01-19 10:18 ` ubizjak at gmail dot com [this message] 2013-01-19 19:46 ` ubizjak at gmail dot com 2013-01-19 21:07 ` ubizjak at gmail dot com 2013-01-21 17:52 ` uros at gcc dot gnu.org 2013-01-21 18:00 ` uros at gcc dot gnu.org 2013-01-21 18:04 ` uros at gcc dot gnu.org 2013-01-21 18:10 ` ubizjak at gmail dot com
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-56023-4-59wd4ueh14@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).