public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38360] [4.3/4.4 regression] ICE in gimple_op, at gimple.h:1636
Date: Tue, 02 Dec 2008 00:36:00 -0000	[thread overview]
Message-ID: <20081202003443.22945.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38360-5724@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from pinskia at gcc dot gnu dot org  2008-12-02 00:34 -------
#1  0x00601a05 in gimple_op (gs=0x42e532d0, i=4) at
/Users/apinski/src/local/gcc/gcc/gimple.h:1636
#2  0x0060578d in gimple_call_arg (gs=0x42e532d0, index=1) at
/Users/apinski/src/local/gcc/gcc/gimple.h:2049
#3  0x0060ee0b in ccp_fold_builtin (stmt=0x42e532d0) at
/Users/apinski/src/local/gcc/gcc/tree-ssa-ccp.c:2567
#4  0x00610218 in fold_gimple_call (gsi=0xbffff63c) at
/Users/apinski/src/local/gcc/gcc/tree-ssa-ccp.c:2793
#5  0x0061092d in fold_stmt (gsi=0xbffff63c) at
/Users/apinski/src/local/gcc/gcc/tree-ssa-ccp.c:2881
#6  0x00525d64 in remove_useless_stmts_1 (gsi=0xbffff63c, data=0xbffff73c) at
/Users/apinski/src/local/gcc/gcc/tree-cfg.c:1921

4.3.2 also ICEs in the same spot so did 4.3.0:
[andrew-pinskis-computer-2:gcc/objdir/stage1-gcc] apinski% ~/local-gcc/bin/gcc
-V4.3.0 t.ct.c: In function 'main':
t.c:5: internal compiler error: tree check: accessed operand 5 of call_expr
with 4 operands in ccp_fold_builtin, at tree-ssa-ccp.c:2466
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
      Known to work|4.3.3                       |
   Last reconfirmed|0000-00-00 00:00:00         |2008-12-02 00:34:43
               date|                            |
            Summary|[4.4 regression] ICE in     |[4.3/4.4 regression] ICE in
                   |gimple_op, at gimple.h:1636 |gimple_op, at gimple.h:1636


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


  parent reply	other threads:[~2008-12-02  0:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  0:18 [Bug middle-end/38360] New: [4.4 " debian-gcc at lists dot debian dot org
2008-12-02  0:25 ` [Bug middle-end/38360] " debian-gcc at lists dot debian dot org
2008-12-02  0:36 ` pinskia at gcc dot gnu dot org [this message]
2008-12-02  0:39 ` [Bug middle-end/38360] [4.3/4.4 " pinskia at gcc dot gnu dot org
2008-12-02  8:03 ` jakub at gcc dot gnu dot org
2008-12-02  8:13 ` jakub at gcc dot gnu dot org
2008-12-02 11:18 ` rguenth at gcc dot gnu dot org
2008-12-03 17:00 ` jakub at gcc dot gnu dot org
2008-12-03 17:05 ` [Bug middle-end/38360] [4.3 " jakub at gcc dot gnu dot org
2008-12-05 12:36 ` [Bug middle-end/38360] [4.3 Regression] " rguenth at gcc dot gnu dot org
2009-01-24 10:27 ` rguenth at gcc dot gnu dot org
2009-08-04 12:45 ` rguenth at gcc dot gnu dot org
2010-04-20 14:25 ` rguenth at gcc dot gnu dot org
2010-04-20 14:25 ` rguenth 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=20081202003443.22945.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).