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 c++/18384] [3.3/3.4/4.0 Regression] ICE on zero-length array with empty initializer...
Date: Tue, 28 Dec 2004 20:58:00 -0000	[thread overview]
Message-ID: <20041228205815.11918.qmail@sourceware.org> (raw)
In-Reply-To: <20041108213431.18384.apl@alum.mit.edu>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-12-28 20:58 -------
Subject: Bug 18384

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	gcc-3_4-branch
Changes by:	jakub@gcc.gnu.org	2004-12-28 20:57:56

Modified files:
	gcc/cp         : ChangeLog 
	gcc/testsuite  : ChangeLog 
	gcc/cp         : decl.c 
Added files:
	gcc/testsuite/g++.dg/init: array18.C 

Log message:
	PR c++/18384, c++/18327
	* decl.c (reshape_init_array): Use UHWI type for max_index_cst
	and index.  Convert max_index to size_type_node if it isn't
	host_integerp (, 1).
	
	* g++.dg/init/array18.C: New test.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.3892.2.188&r2=1.3892.2.189
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.3389.2.337&r2=1.3389.2.338
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/decl.c.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.1174.2.28&r2=1.1174.2.29
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/init/array18.C.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=NONE&r2=1.1.2.1



-- 


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


  parent reply	other threads:[~2004-12-28 20:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 21:34 [Bug c++/18384] New: " apl at alum dot mit dot edu
2004-11-08 22:09 ` [Bug c++/18384] " apl at alum dot mit dot edu
2004-11-08 22:12 ` [Bug c++/18384] [3.3/3.4/4.0 Regression] " pinskia at gcc dot gnu dot org
2004-11-12 18:20 ` mmitchel at gcc dot gnu dot org
2004-11-18  1:44 ` giovannibajo at libero dot it
2004-11-18  7:59 ` mark at codesourcery dot com
2004-11-18  9:00 ` giovannibajo at libero dot it
2004-11-20 18:33 ` pinskia at gcc dot gnu dot org
2004-11-21 22:53 ` giovannibajo at libero dot it
2004-11-23  1:17 ` mmitchel at gcc dot gnu dot org
2004-12-10 13:27 ` pinskia at gcc dot gnu dot org
2004-12-15 13:36 ` pinskia at gcc dot gnu dot org
2004-12-27 15:47 ` pinskia at gcc dot gnu dot org
2004-12-27 17:18 ` mmitchel at gcc dot gnu dot org
2004-12-27 21:57 ` giovannibajo at libero dot it
2004-12-28 20:58 ` cvs-commit at gcc dot gnu dot org [this message]
2004-12-29 18:54 ` gdr at integrable-solutions dot net
2005-02-07 21:12 ` giovannibajo at libero dot it
2005-02-25 16:01 ` steven at gcc dot gnu dot org
2005-02-25 16:20 ` jakub at gcc dot gnu dot org
2005-02-28 16:23 ` [Bug c++/18384] [3.3/3.4/4.0/4.1 " cvs-commit at gcc dot gnu dot org
2005-03-10 14:19 ` cvs-commit at gcc dot gnu dot org
2005-03-10 14:21 ` cvs-commit at gcc dot gnu dot org
2005-03-10 14:23 ` [Bug c++/18384] [3.3 " jakub at gcc dot gnu dot org
2005-04-30 13:08 ` gdr at gcc dot gnu dot org
2005-04-30 13:26 ` gdr at gcc dot gnu dot org
2005-05-02 11:13 ` reichelt 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=20041228205815.11918.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).