public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19164] [3.3/3.4/4.0 Regression] ICE in digest_init or build_vector
Date: Wed, 19 Jan 2005 09:28:00 -0000	[thread overview]
Message-ID: <20050119092755.3771.qmail@sourceware.org> (raw)
In-Reply-To: <20041227131304.19164.jakub@gcc.gnu.org>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-01-19 09:27 -------
Subject: Bug 19164

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	jakub@gcc.gnu.org	2005-01-19 09:27:24

Modified files:
	gcc            : ChangeLog c-typeck.c gimplify.c 
	gcc/testsuite  : ChangeLog 
Added files:
	gcc/testsuite/gcc.c-torture/compile: 20050113-1.c 
	gcc/testsuite/gcc.dg: 20050113-1.c 

Log message:
	PR c/17297
	* c-typeck.c (digest_init): Only call build_vector if all constructor
	elements are *_CST nodes.
	* gimplify.c (gimplify_init_constructor): Likewise.
	
	* gcc.c-torture/compile/20050113-1.c: New testcase.
	
	PR middle-end/19164
	* c-typeck.c (digest_init): Only call build_vector if inside_init
	is a CONSTRUCTOR.
	
	* gcc.dg/20050113-1.c: New testcase.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.7183&r2=2.7184
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/c-typeck.c.diff?cvsroot=gcc&r1=1.410&r2=1.411
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/gimplify.c.diff?cvsroot=gcc&r1=2.103&r2=2.104
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.4907&r2=1.4908
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gcc.c-torture/compile/20050113-1.c.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gcc.dg/20050113-1.c.diff?cvsroot=gcc&r1=NONE&r2=1.1



-- 


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


  parent reply	other threads:[~2005-01-19  9:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-27 13:13 [Bug middle-end/19164] New: " jakub at gcc dot gnu dot org
2004-12-28 20:57 ` [Bug middle-end/19164] [3.3/3.4/4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-13 18:17 ` pinskia at gcc dot gnu dot org
2005-01-19  9:28 ` cvs-commit at gcc dot gnu dot org [this message]
2005-01-19  9:45 ` cvs-commit at gcc dot gnu dot org
2005-01-19  9:53 ` [Bug middle-end/19164] [3.3 " jakub at gcc dot gnu dot org
2005-04-30 13:16 ` gdr at gcc dot gnu dot org
2005-04-30 13:23 ` gdr 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=20050119092755.3771.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).