public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	sbdep@woot.net
Subject: Re: other/10294: ICE when declaring a variable within switch statement
Date: Wed, 02 Apr 2003 21:59:00 -0000	[thread overview]
Message-ID: <20030402215951.10692.qmail@sources.redhat.com> (raw)

Synopsis: ICE when declaring a variable within switch statement

State-Changed-From-To: open->closed
State-Changed-By: cae
State-Changed-When: Wed Apr  2 21:59:51 2003
State-Changed-Why:
    I can confirm this with 3.2.3, the condition is that the
    class has a destructor. A reduced testcase is:
    
    struct vector
    {
      vector () {}
      ~vector() {}
    };
    int main (int argc)
    {
            switch (argc) {
                    vector c;
            case '3':
                    break;
            }
            return 0;
    }
    
    However, this is fixed in 3.3 and 3.4 and 3.2 gives a reasonable
    error message before the ICE, i.e. this will not give the
    Internal Compiler Error message on the release, instead it will
    say something like "confused by earlier error. Bailing out."
    The summary of all this is, that this bug probably won't be fixed
    for 3.2 anymore.
    
       regards   Christian
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10294


             reply	other threads:[~2003-04-02 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02 21:59 ehrhardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-02  7:16 sbdep

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=20030402215951.10692.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=sbdep@woot.net \
    /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).