public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/28915] [4.1 regression] ICE: tree check: expected class 'constant', have 'declaration' (var_decl) in build_vector, at tree.c:973
Date: Mon, 13 Nov 2006 23:31:00 -0000	[thread overview]
Message-ID: <20061113233128.20269.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28915-12387@http.gcc.gnu.org/bugzilla/>



------- Comment #22 from jason at gcc dot gnu dot org  2006-11-13 23:31 -------
Subject: Bug 28915

Author: jason
Date: Mon Nov 13 23:31:16 2006
New Revision: 118786

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=118786
Log:
        PR middle-end/28915
        * gimplify.c (gimplify_init_constructor): Don't reduce TREE_CONSTANT
        vector ctors.
        * tree-cfg.c (verify_expr): Don't look into TREE_CONSTANT
        vector ctors.
        * expmed.c (make_tree): Handle CONST, SYMBOL_REF.
        * tree.c (build_vector): Handle non-_CST elements.

Added:
    branches/gcc-4_1-branch/gcc/testsuite/gcc.target/i386/vectorize1.c
      - copied unchanged from r118747,
trunk/gcc/testsuite/gcc.target/i386/vectorize1.c
Modified:
    branches/gcc-4_1-branch/gcc/ChangeLog
    branches/gcc-4_1-branch/gcc/expmed.c
    branches/gcc-4_1-branch/gcc/gimplify.c
    branches/gcc-4_1-branch/gcc/testsuite/ChangeLog
    branches/gcc-4_1-branch/gcc/tree-cfg.c
    branches/gcc-4_1-branch/gcc/tree.c


-- 


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


  parent reply	other threads:[~2006-11-13 23:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-31 12:24 [Bug tree-optimization/28915] New: [4.2 " tbm at cyrius dot com
2006-08-31 12:30 ` [Bug tree-optimization/28915] " tbm at cyrius dot com
2006-08-31 16:13 ` pinskia at gcc dot gnu dot org
2006-08-31 19:15 ` uros at kss-loka dot si
2006-08-31 19:21 ` pinskia at gcc dot gnu dot org
2006-08-31 19:28 ` tbm at cyrius dot com
2006-09-01  6:27 ` pinskia at gcc dot gnu dot org
2006-09-01 22:32 ` mmitchel at gcc dot gnu dot org
2006-09-04 17:07 ` [Bug middle-end/28915] " pinskia at gcc dot gnu dot org
2006-09-05  4:20 ` pinskia at gcc dot gnu dot org
2006-09-06  6:30 ` pinskia at gcc dot gnu dot org
2006-09-06  6:33 ` pinskia at gcc dot gnu dot org
2006-09-06 15:27 ` roger at eyesopen dot com
2006-09-06 15:37 ` roger at eyesopen dot com
2006-09-09  6:44 ` jason at gcc dot gnu dot org
2006-09-10  0:48 ` jason at gcc dot gnu dot org
2006-09-22  4:36 ` rsandifo at gcc dot gnu dot org
2006-10-01  4:33 ` [Bug middle-end/28915] [4.1/4.2 " pinskia at gcc dot gnu dot org
2006-11-11  2:19 ` [Bug middle-end/28915] [4.1/4.2/4.3 " roger at eyesopen dot com
2006-11-13  8:16 ` jason at gcc dot gnu dot org
2006-11-13  8:19 ` jason at gcc dot gnu dot org
2006-11-13 14:41 ` [Bug middle-end/28915] [4.1 " pinskia at gcc dot gnu dot org
2006-11-13 18:53 ` hjl at gcc dot gnu dot org
2006-11-13 18:55 ` hjl at gcc dot gnu dot org
2006-11-13 23:31 ` jason at gcc dot gnu dot org [this message]
2006-11-13 23:42 ` jason at gcc dot gnu dot org
2006-11-14  9:30 ` jakub at gcc dot gnu dot org
2006-11-14 10:02   ` Andrew Pinski
2006-11-14 10:03 ` pinskia at gmail dot com
2006-12-01  1:09 ` chaoyingfu 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=20061113233128.20269.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).