public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/20928] [4.0/4.1 regression] ICE: unrecognizable insns
Date: Sun, 10 Apr 2005 17:39:00 -0000	[thread overview]
Message-ID: <20050410173937.3213.qmail@sourceware.org> (raw)
In-Reply-To: <20050410150728.20928.aj@gcc.gnu.org>


------- Additional Comments From steven at gcc dot gnu dot org  2005-04-10 17:39 -------
The offending insn is created by emit_move_insn in loop.c, here: 
2354                start_sequence (); 
2355                emit_move_insn (m->insert_temp ? newreg : m->set_dest, 
2356                                m->set_src); 
2357                seq = get_insns (); 
2358                end_sequence (); 
 
(gdb) p debug_rtx_list (seq, 10) 
(insn 45 0 46 (set (reg:DI 69) 
        (mem/u/c:DI (const:DI (unspec:DI [ 
                        (symbol_ref:DI ("bar") [flags 0x40] <var_decl 
0x2a95a2f000 bar>) 
                    ] 2)) [0 S8 A8])) -1 (nil) 
    (nil)) 
 
(insn 46 45 0 (set (reg/f:DI 67) 
        (plus:DI (reg:DI 69) 
            (const_int 2147483648 [0x80000000]))) -1 (nil) 
    (expr_list:REG_EQUAL (const:DI (plus:DI (symbol_ref:DI ("bar") [flags 
0x40] <var_decl 0x2a95a2f000 bar>) 
                (const_int 2147483648 [0x80000000]))) 
        (nil))) 
 
 

-- 


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


  parent reply	other threads:[~2005-04-10 17:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10 15:07 [Bug target/20928] New: ICE: unrecognoizable insns aj at gcc dot gnu dot org
2005-04-10 15:08 ` [Bug target/20928] ICE: unrecognizable insns aj at gcc dot gnu dot org
2005-04-10 15:08 ` aj at gcc dot gnu dot org
2005-04-10 16:02 ` steven at gcc dot gnu dot org
2005-04-10 16:03 ` [Bug target/20928] [4.0/4.1 regression] " steven at gcc dot gnu dot org
2005-04-10 16:08 ` steven at gcc dot gnu dot org
2005-04-10 17:24 ` steven at gcc dot gnu dot org
2005-04-10 17:39 ` steven at gcc dot gnu dot org [this message]
2005-04-10 17:52 ` steven at gcc dot gnu dot org
2005-04-10 19:03 ` steven at gcc dot gnu dot org
2005-04-10 21:05 ` steven at gcc dot gnu dot org
2005-04-21  5:06 ` mmitchel at gcc dot gnu dot org
2005-05-21  7:00 ` aj at gcc dot gnu dot org
2005-06-08  0:09 ` rth at gcc dot gnu dot org
2005-07-06 17:03 ` mmitchel at gcc dot gnu dot org
2005-09-27 16:24 ` mmitchel at gcc dot gnu dot org
     [not found] <bug-20928-260@http.gcc.gnu.org/bugzilla/>
2005-10-10  3:20 ` kazu at gcc dot gnu dot org
2005-10-13 16:03 ` pinskia 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=20050410173937.3213.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).