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/52203] ICE: in reset_sched_cycles_in_current_ebb, at sel-sched.c:7136 with -fsel-sched-pipelining -fselective-scheduling2 and other custom flags
Date: Mon, 13 Feb 2012 15:54:00 -0000	[thread overview]
Message-ID: <bug-52203-4-O2hvEE6eUz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52203-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Uros Bizjak <ubizjak at gmail dot com> 2012-02-13 15:54:28 UTC ---
(In reply to comment #2)
> Well, in this case the insn is vcvtps2pd (from avx_cvtps2pd256 and
> *avx_cvtps2pd256_2 patterns) but not having a reservation looks correct as the
> manual says "decode type -- microcode".  Uros, is that right?  In this case,
> the below fixes the test for me (and I was stupid enough not to do this in the
> first place when this bug stream just started...  However, we did fix some real
> bugs.)

There is nothing wrong with insn definition, the problem is only that
attributes are missing.  Attributes are considered a tool to fine-tune the
scheduler and in any case, gcc should not ICE on an insn without reservation.
The insn doesn't reserve anything in this case and scheduler should live with
this.

The bugs you are referring to were real bugs, where wrong or missing operand
was accessed from attribute calculation machinery.


  parent reply	other threads:[~2012-02-13 15:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 22:19 [Bug rtl-optimization/52203] New: " zsojka at seznam dot cz
2012-02-10 22:43 ` [Bug rtl-optimization/52203] " steven at gcc dot gnu.org
2012-02-11 12:53 ` abel at gcc dot gnu.org
2012-02-13  8:49 ` abel at gcc dot gnu.org
2012-02-13  8:49 ` abel at gcc dot gnu.org
2012-02-13 15:54 ` ubizjak at gmail dot com [this message]
2012-02-13 16:01 ` ubizjak at gmail dot com
2012-02-13 16:02 ` ubizjak at gmail dot com
2012-02-13 21:14 ` steven at gcc dot gnu.org
2012-02-14  6:57 ` abel at gcc dot gnu.org
2012-03-07 12:01 ` abel at gcc dot gnu.org
2012-03-07 12:03 ` abel at gcc dot gnu.org
2012-04-13  9:37 ` 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-52203-4-O2hvEE6eUz@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).