public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/28879] [4.0/4.1/4.2 regression] ICE with variable-sized array in template function Date: Tue, 29 Aug 2006 02:44:00 -0000 [thread overview] Message-ID: <20060829024438.21967.qmail@sourceware.org> (raw) In-Reply-To: <bug-28879-1771@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from pinskia at gcc dot gnu dot org 2006-08-29 02:44 ------- Actually the second case is because we call: 426 t = build_array_type (elt_type, index_type); #12 0x081e0cae in build_cplus_array_type_1 (elt_type=0xb7c62284, index_type=0xb7d055c0) at ../../gcc/cp/tree.c:426 And the first problem was introduced with an ABI change: 6524 if (abi_version_at_least (2) 6525 /* We should only handle value dependent expressions specially. */ 6526 ? value_dependent_expression_p (size) #3 0x08084f4f in compute_array_index_type (name=0xb7cea09c, size=0xb7cba0c8) at ../../gcc/cp/decl.c:6524 If you do -fabi-version=1, we get the ICE later on but with the same problem: 417 if (dependent_type_p (elt_type) 418 || (index_type 419 && value_dependent_expression_p (TYPE_MAX_VALUE (index_type)))) #4 0x081e0c31 in build_cplus_array_type_1 (elt_type=0xb7cf0284, index_type=0xb7d93564) at ../../gcc/cp/tree.c:417 -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2006-08-29 02:44:38 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28879
next prev parent reply other threads:[~2006-08-29 2:44 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-08-28 23:48 [Bug c++/28879] New: " reichelt at gcc dot gnu dot org 2006-08-28 23:48 ` [Bug c++/28879] " reichelt at gcc dot gnu dot org 2006-08-28 23:57 ` pinskia at gcc dot gnu dot org 2006-08-29 2:44 ` pinskia at gcc dot gnu dot org [this message] 2006-09-01 22:17 ` mmitchel at gcc dot gnu dot org 2006-10-17 3:06 ` [Bug c++/28879] [4.0/4.1/4.2 regression] ICE with VLA " mmitchel at gcc dot gnu dot org 2007-02-03 19:42 ` [Bug c++/28879] [4.0/4.1/4.2/4.3 " gdr at gcc dot gnu dot org 2007-02-03 20:55 ` pinskia at gcc dot gnu dot org 2007-02-14 9:16 ` mmitchel at gcc dot gnu dot org 2007-03-07 22:39 ` pinskia at gcc dot gnu dot org 2007-11-19 23:31 ` jakub at gcc dot gnu dot org 2007-11-20 6:39 ` jakub at gcc dot gnu dot org 2008-02-13 18:14 ` jason at gcc dot gnu dot org 2008-02-13 18:19 ` mark at codesourcery dot com 2008-07-04 21:29 ` [Bug c++/28879] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2009-03-20 19:37 ` jason at gcc dot gnu dot org 2009-03-21 20:16 ` jason at gcc dot gnu dot org 2009-03-21 20:51 ` jason at gcc dot gnu dot org 2009-03-21 21:14 ` [Bug c++/28879] [4.2/4.3 Regression] " rguenth at gcc dot gnu dot org 2009-03-22 3:07 ` jason at gcc dot gnu dot org 2009-03-31 19:41 ` [Bug c++/28879] [4.3 " jsm28 at gcc dot gnu dot org 2009-08-04 12:35 ` rguenth at gcc dot gnu dot org 2010-04-20 13:25 ` rguenth 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=20060829024438.21967.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: linkBe 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).