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++/18327] [3.3/3.4/4.0 Regression] ICE while compiling valid c code with g++ Date: Sun, 07 Nov 2004 01:56:00 -0000 [thread overview] Message-ID: <20041107015624.8948.qmail@sourceware.org> (raw) In-Reply-To: <20041106234911.18327.wolf@pld-linux.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-07 01:56 ------- Confirmed, reduced testcase: typedef struct { unsigned char dir; int data[]; } AiDefaultRailBlock; static const AiDefaultRailBlock _raildata_ai_0 = { 1, { 0, 4 } }; : Search converges between 2004-09-21-004002-3.4 (#77) and 2004-09-22-004001-3.4 (#78). : Search converges between 2004-09-20-161001-trunk (#551) and 2004-09-21-094824-trunk (#552). : Search converges between 2004-09-20-064502-3.3 (#296) and 2004-09-27-064501-3.3 (#297). The only thing which went in all three branches around this time was: 2004-09-20 Giovanni Bajo <giovannibajo@gcc.gnu.org> PR c++/14179 * decl.c (reshape_init): Extract array handling into... (reshape_init_array): New function. Use integers instead of trees for indices. Handle out-of-range designated initializers. Also that did change how initialization was done. (This is valid C but is/should it be valid C++) -- What |Removed |Added ---------------------------------------------------------------------------- CC| |giovannibajo at gcc dot gnu | |dot org, gdr at gcc dot gnu | |dot org Status|UNCONFIRMED |NEW Ever Confirmed| |1 Known to fail| |3.4.3 4.0.0 Known to work| |3.4.0 Last reconfirmed|0000-00-00 00:00:00 |2004-11-07 01:56:23 date| | Summary|ICE while compiling valid c |[3.3/3.4/4.0 Regression] ICE |code with g++ |while compiling valid c code | |with g++ Target Milestone|--- |3.4.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18327
next prev parent reply other threads:[~2004-11-07 1:56 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-06 23:49 [Bug c++/18327] New: " gcc-bugzilla at gcc dot gnu dot org 2004-11-06 23:52 ` [Bug c++/18327] " pinskia at gcc dot gnu dot org 2004-11-07 0:09 ` wolf at pld-linux dot org 2004-11-07 0:11 ` pinskia at gcc dot gnu dot org 2004-11-07 1:56 ` pinskia at gcc dot gnu dot org [this message] 2004-11-07 8:56 ` [Bug c++/18327] [3.3/3.4/4.0 Regression] " giovannibajo at libero dot it 2004-11-18 12:14 ` pinskia at gcc dot gnu dot org 2004-12-10 16:09 ` pinskia at gcc dot gnu dot org 2005-01-23 20:35 ` pinskia at gcc dot gnu dot org 2005-02-15 21:03 ` pinskia at gcc dot gnu dot org 2005-02-15 23:36 ` pinskia at gcc dot gnu dot org 2005-03-10 15:13 ` [Bug c++/18327] [3.3 " pinskia at gcc dot gnu dot org 2005-04-30 13:26 ` gdr at gcc dot gnu dot org 2005-05-19 17:33 ` mmitchel at gcc dot gnu dot org 2005-05-22 21:00 ` pinskia 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=20041107015624.8948.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).