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] [4.1 Regression] ICE in ssa tree check compiling crafty with -ftree-vectorize -maltivec
Date: Fri, 29 Apr 2005 22:28:00 -0000	[thread overview]
Message-ID: <20050429222755.5775.qmail@sourceware.org> (raw)
In-Reply-To: <20050421230833.21155.janis@gcc.gnu.org>


------- Additional Comments From janis at gcc dot gnu dot org  2005-04-29 22:27 -------
Today I'm seeing the same ICE building mesa and sometimes building 176.gcc.
Tests apsi. fma3d, gap, and gcc all cause GCC to segfault with "-O2
-ftree-vectorize -maltivec", some with -m32, some with -m64, and some with
both; some ICE in multiple source files for the same test (I'm using -j8).
Using a .i file sometimes makes the problem disappear, as do small changes
to the source code or using gdb.

I realize this isn't particularly helpful, but I wanted to record the failures
I'm seeing so that whoever looks into this doesn't give up if the problem
seems to have gone away.

-- 


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


  parent reply	other threads:[~2005-04-29 22:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 23:08 [Bug tree-optimization/21155] New: " janis at gcc dot gnu dot org
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 [this message]
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=20050429222755.5775.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).