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 middle-end/55889] [4.8 Regression] ICE: in move_op_ascend, at sel-sched.c:6153 with -fschedule-insns -fselective-scheduling
Date: Fri, 18 Jan 2013 11:09:00 -0000	[thread overview]
Message-ID: <bug-55889-4-FqVp3Cmry6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55889-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #8 from Andrey Belevantsev <abel at gcc dot gnu.org> 2013-01-18 11:09:13 UTC ---
Created attachment 29202
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29202
more debug printing patch

>From the log, the problem looks as follows.  There is 

insn 24, %3=[unspec[`*LCM..2',%2], 

which is allowed to move past 

insn 17, {%3=unspec[%3,%4] 25;clobber %0;clobber %4;clobber %5;clobber
%11;clobber %0;clobber lr;}, 

given that its target register will be renamed.  After renaming, it shows as 

insn 145, r192=[unspec[`*LCM..2',%2] 44]

but this insn is suddenly can not be moved through insn 17, thus the scheduler
aborts.  The question is why insn 145 or insn 23, which looks like
r148=[unspec[`*LC..2',%2] 44] (same unspec code, etc), cannot be moved through
insn 17 while insn 24 can.  

Attached is the patch that produces lots of debug output from the dependency
analysis.  David, could you apply it on top of the previous one and run the
test case with -fsched-verbose=9 this time?  (It uses libbacktrace, I'm not
sure whether AIX is fine with that, but even without this there will be a lot
more information.)  Also, if you can clarify the above question on what is
different between insns 23/145 and 24 from the target point of view, it would
help a lot.


  parent reply	other threads:[~2013-01-18 11:09 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06 18:55 [Bug middle-end/55889] New: " dje at gcc dot gnu.org
2013-01-06 18:56 ` [Bug middle-end/55889] " dje at gcc dot gnu.org
2013-01-07 15:55 ` rguenth at gcc dot gnu.org
2013-01-08 12:19 ` jakub at gcc dot gnu.org
2013-01-08 21:56 ` dje at gcc dot gnu.org
2013-01-09  2:53 ` dje at gcc dot gnu.org
2013-01-09 14:26 ` abel at gcc dot gnu.org
2013-01-11 14:24 ` abel at gcc dot gnu.org
2013-01-11 14:38 ` dje at gcc dot gnu.org
2013-01-18 11:09 ` abel at gcc dot gnu.org [this message]
2013-01-18 16:49 ` dje at gcc dot gnu.org
2013-01-18 16:57 ` dje at gcc dot gnu.org
2013-01-21 10:16 ` abel at gcc dot gnu.org
2013-01-21 12:53 ` jakub at gcc dot gnu.org
2013-01-21 13:24 ` abel at gcc dot gnu.org
2013-01-21 15:14 ` dje at gcc dot gnu.org
2013-01-21 15:16 ` dje at gcc dot gnu.org
2013-01-21 15:25 ` jakub at gcc dot gnu.org
2013-01-21 15:38 ` dje at gcc dot gnu.org
2013-01-21 15:42 ` dje at gcc dot gnu.org
2013-01-21 15:54 ` jakub at gcc dot gnu.org
2013-01-21 17:32 ` abel at gcc dot gnu.org
2013-01-23 11:11 ` abel at gcc dot gnu.org
2013-01-24  2:36 ` dje at gcc dot gnu.org
2013-01-24 13:37 ` abel at gcc dot gnu.org
2013-01-24 16:37 ` dje at gcc dot gnu.org
2013-01-31 17:50 ` dje at gcc dot gnu.org
2013-02-01 12:22 ` abel at gcc dot gnu.org
2013-02-06 21:38 ` vmakarov at gcc dot gnu.org
2013-02-14  6:11 ` abel at gcc dot gnu.org
2013-02-14 16:48 ` vmakarov at redhat dot com
2013-02-15 13:48 ` abel at gcc dot gnu.org
2013-02-15 16:15 ` dje at gcc dot gnu.org
2013-02-19 13:51 ` abel at gcc dot gnu.org
2013-02-19 13:55 ` abel at gcc dot gnu.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-55889-4-FqVp3Cmry6@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: 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).