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 target/41551] ia64: ICE: in instantiate_virtual_regs_in_insn, at function.c:1630
Date: Fri, 02 Oct 2009 21:04:00 -0000	[thread overview]
Message-ID: <20091002210442.1617.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41551-18261@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from jakub at gcc dot gnu dot org  2009-10-02 21:04 -------
Perhaps better don't do something as non-sensical as this.

Anyway, we shouldn't ICE on it.

--- function.c.jj        2009-09-29 15:10:43.000000000 +0200
+++ function.c        2009-10-02 23:01:49.000000000 +0200
@@ -1598,7 +1598,10 @@ instantiate_virtual_regs_in_insn (rtx in
       if (!safe_insn_predicate (insn_code, i, x))
         {
           start_sequence ();
-          x = force_reg (insn_data[insn_code].operand[i].mode, x);
+          if (REG_P (x))
+            x = copy_to_reg (x);
+          else
+            x = force_reg (insn_data[insn_code].operand[i].mode, x);
           seq = get_insns ();
           end_sequence ();
           if (seq)

should fix this.


-- 


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


  reply	other threads:[~2009-10-02 21:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 19:22 [Bug target/41551] New: " gcc-bugzilla at gcc dot gnu dot org
2009-10-02 21:04 ` jakub at gcc dot gnu dot org [this message]
2009-11-30 22:11 ` [Bug middle-end/41551] " sje at cup dot hp dot com
2010-08-09 16:28 ` armin76 at gentoo dot org
2010-08-09 17:11 ` [Bug middle-end/41551] [4.4 Regression] " steven at gcc dot gnu dot org
2010-08-09 17:12 ` steven at gcc dot gnu dot org
2010-08-10 15:41 ` sje at gcc dot gnu dot org
2010-08-10 15:59 ` sje at cup dot hp 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=20091002210442.1617.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).