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 tree-optimization/33453] [4.3 Regression] ICE in build2_stat, at tree.c:3110 with -ftree-parallelize-loops=4 -ftree-vectorize
Date: Mon, 03 Dec 2007 15:00:00 -0000	[thread overview]
Message-ID: <20071203150003.20867.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33453-1649@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from jakub at gcc dot gnu dot org  2007-12-03 15:00 -------
This isn't one bug, but many unrelated ones.
I have a fix for #c3 testcase, a fix for the p+ issue in the initial testcase
and also a different ICE with missing DECL_GIMPLE_REG_P created by parloop.
But those aren't the only ones, when that is fixed, it ICEs again in completely
different spot, I'm afraid the parloop pass still has lots of issues (but those
shouldn't be considered regressions, at least not P2 ones, given that it is a
new pass).

Here is a cleaned up alternative to the initial testcase which doesn't use
undefined vars etc.:
/* { dg-do compile } */
/* { dg-options "-O3 -ftree-parallelize-loops=4" } */
struct T
{
  int t;
  struct { short s1, s2, s3, s4 } *s;
};
void
Create_BCyl (int *a, int *b, int *c, int *d, struct T *e)
{
  int i;
  for (i = 0; i < e->t; i++)
    {
      e->s[i].s1 = a[i];
      e->s[i].s2 = b[i];
      e->s[i].s3 = c[i];
      e->s[i].s4 = d[i];
    }
}

I guess I'll leave the rest to Zdenek/Sebastian once I have tested/posted the
fixes I have.


-- 

jakub at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2007-12-03 13:59:02         |2007-12-03 15:00:02
               date|                            |


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


  parent reply	other threads:[~2007-12-03 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17  6:51 [Bug tree-optimization/33453] New: " ubizjak at gmail dot com
2007-09-17  9:14 ` [Bug tree-optimization/33453] " pinskia at gcc dot gnu dot org
2007-09-17 11:03 ` rguenth at gcc dot gnu dot org
2007-11-17 16:09 ` tbm at cyrius dot com
2007-11-17 16:12 ` tbm at cyrius dot com
2007-11-23 22:29 ` rguenth at gcc dot gnu dot org
2007-11-23 22:34 ` [Bug tree-optimization/33453] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-11-27  5:51 ` mmitchel at gcc dot gnu dot org
2007-12-03 13:59 ` jakub at gcc dot gnu dot org
2007-12-03 15:00 ` jakub at gcc dot gnu dot org [this message]
2007-12-03 22:36 ` jakub at gcc dot gnu dot org
2007-12-03 22:44 ` jakub 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=20071203150003.20867.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).