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: Mon, 21 Jan 2013 10:16:00 -0000	[thread overview]
Message-ID: <bug-55889-4-qD4CDiveuY@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 #11 from Andrey Belevantsev <abel at gcc dot gnu.org> 2013-01-21 10:15:31 UTC ---
(In reply to comment #10)
> Neither insn 24/145 nor insn 28 move through insn 17. The two UNSPEC 44 insn
> (LC..2,, LCM..2) are inputs to insn 17. The pseudos are moved into r3 and r4,
> which are the inputs to insn 17.

You mean insn 23, not insn 28, right?  I'm not sure how insns 23/24 could be
inputs to insn 17, as they move up through insn 17.  I don't see full RTL so
I'm guessing here.

Unfortunately, libbacktrace didn't work for the dump you provided, so I only
see that for insn 23 we generate a "general dependency" meaning that it is not
connected to lhs or rhs of the insn, but I don't know where exactly it comes
from.  We do not generate such dependency for insn 24, while they differ only
in lhs -- the former having a pseudo, the latter a hard register r3.  I think
this could be fixed by making the same kind of dependency for insn 24, but I'm
unable to make the compiler generate it, as to get insn 17 I need TLS support
not available in the cross compiler.  

In general, would you allow insn 24 to move past insn 17 with the new register
or does it have to be r3 in insn 24?


  parent reply	other threads:[~2013-01-21 10:16 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
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 [this message]
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-qD4CDiveuY@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).