public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/21155] New: ICE in ssa tree check compiling crafty with -ftree-vectorize -maltivec
Date: Thu, 21 Apr 2005 23:08:00 -0000	[thread overview]
Message-ID: <20050421230833.21155.janis@gcc.gnu.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]

GCC mainline gets an ICE compiling crafty from SPEC CPU2000 on
powerpc64-linux:
                                                                                
elm3b149% /home/janis/tools/gcc-mline-20050421/bin/gcc -m64 -O2 -ftree-vectorize
-maltivec -c crafty_bug.c
crafty_bug.c: In function ‘main’:
crafty_bug.c:31: internal compiler error: tree check: expected ssa_name, have
var_decl in ssa_mark_def_sites, at tree-into-ssa.c:3055
                                                                                
The test case, extracted from crafty's main.c, is still pretty big,
but taking out anything else made it work.  I tried it on another
system where it got a segfault instead, and some small changes caused
segfaults with the compiler which I was reducing it.
                                                                                
I first see the ICE with this patch from law but it might merely be
a latent bug, particularly since the test case is so touchy:
                                                                                
   http://gcc.gnu.org/ml/gcc-cvs/2005-04/msg00808.html

-- 
           Summary: ICE in ssa tree check compiling crafty with -ftree-
                    vectorize -maltivec
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: janis at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: powerpc64-linux
  GCC host triplet: powerpc64-linux
GCC target triplet: powerpc64-linux


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


             reply	other threads:[~2005-04-21 23:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 23:08 janis at gcc dot gnu dot org [this message]
2005-04-21 23:09 ` [Bug tree-optimization/21155] " janis at gcc dot gnu dot org
2005-04-22 19:10 ` [Bug tree-optimization/21155] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-04-29 22:28 ` janis at gcc dot gnu dot org
2005-04-29 22:39 ` janis at gcc dot gnu dot org
2005-05-16 20:41 ` janis at gcc dot gnu dot org
2005-05-26 18:54 ` pinskia at gcc dot gnu dot org
2005-05-30 14:49 ` dorit at il dot ibm dot com
2005-05-30 17:07 ` pinskia at gcc dot gnu dot org
2005-05-31 22:14 ` janis at gcc dot gnu dot org
2005-06-01 11:24 ` dorit at il dot ibm dot com
2005-06-11 14:22 ` reichelt at gcc dot gnu dot org
2005-06-13 17:45 ` janis at gcc dot gnu dot org
2005-06-13 17:49 ` 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=20050421230833.21155.janis@gcc.gnu.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).