public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Bas Wijnen <b.wijnen@student.rug.nl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/5434: g++ ICEs on construction of variable sized object Date: Sat, 19 Jan 2002 13:16:00 -0000 [thread overview] Message-ID: <20020119211601.28628.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/5434; it has been noted by GNATS. From: Bas Wijnen <b.wijnen@student.rug.nl> To: rodrigc@gcc.gnu.org, b.wijnen@student.rug.nl, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/5434: g++ ICEs on construction of variable sized object Date: Sat, 19 Jan 2002 22:01:19 +0100 Hmm, right. I installed a debian system with gcc and g++ without really looking which version. I now see I have both 2.95 and 3.0 installed. gccbug<tab> just appended -3.0, so I thought that would be the version I have installed, not realizing I had two versions installed. Thank you for the fast reply. I didn't actually need the answer, so I was not planning to take any other action. If I should, please let me know. Bye, Bas Wijnen On Sat, Jan 19, 2002 at 06:42:55PM -0000, rodrigc@gcc.gnu.org wrote: > Synopsis: g++ ICEs on construction of variable sized object > > State-Changed-From-To: open->closed > State-Changed-By: rodrigc > State-Changed-When: Sat Jan 19 10:42:54 2002 > State-Changed-Why: > Why are you compiling with gcc 2.95.4 but reporting this > as a bug in gcc 3.0.3? > > Your test case does not ICE with gcc 3.0.3 > or gcc 3.1 in CVS, but it produces an error: > data.h:17: size of member `realdata' is not constant > > Your workaround of using a #define is valid. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5434
next reply other threads:[~2002-01-19 21:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-19 13:16 Bas Wijnen [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-19 10:42 rodrigc 2002-01-19 8:26 b.wijnen
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=20020119211601.28628.qmail@sources.redhat.com \ --to=b.wijnen@student.rug.nl \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).