public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/45136] -fcompare-debug failure with -Os -fschedule-insns
Date: Fri, 30 Jul 2010 09:41:00 -0000	[thread overview]
Message-ID: <20100730094058.28167.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45136-14164@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from jakub at gcc dot gnu dot org  2010-07-30 09:40 -------
Confirmed, this seems to be sched1 fault.
In bb5 we have 2 normal insns, followed by (-g only) a debug_insn, followed by
two NOTE_INSN_DELETED created by combine (do we ever remove these from the
IL?),
followed again (-g only) by debug_insn and then other insns.
sched1 moves those two NOTE_INSN_DELETED in -g case to the start of the block,
keeps them where they were otherwise.

Alex, can you please have a look?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45136


  parent reply	other threads:[~2010-07-30  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 20:20 [Bug rtl-optimization/45136] New: " zsojka at seznam dot cz
2010-07-29 20:21 ` [Bug rtl-optimization/45136] " zsojka at seznam dot cz
2010-07-30  0:33 ` hjl dot tools at gmail dot com
2010-07-30  1:35 ` zsojka at seznam dot cz
2010-07-30  4:11 ` hjl dot tools at gmail dot com
2010-07-30  9:41 ` jakub at gcc dot gnu dot org [this message]
2010-08-30 19:14 ` aoliva at gcc dot gnu dot org
2010-08-30 19:14 ` aoliva at gcc dot gnu dot org
2010-09-04 15:28 ` [Bug debug/45136] " aoliva at gcc dot gnu 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=20100730094058.28167.qmail@sourceware.org \
    --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: link
Be 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).