public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/21113] New: Jumps into VLA or VM scope not rejected for C++
Date: Tue, 19 Apr 2005 21:20:00 -0000	[thread overview]
Message-ID: <20050419212056.21113.jsm28@gcc.gnu.org> (raw)

Jumps into the scope of an identifier with variably modified type (with goto or
switch) are not rejected by the C++ front end.  Bug 12913 describes this problem
for C, but there should be a separate bug for C++ since bug 16989 only depends
on the issue being fixed for C and not for C++.  The examples in bug 12913 apply:

void f(int l) { 
  goto label; 
  int a[l]; 
 label:; 
} 
    
void g (int l) {
  switch (l) {
  case 1:;
    int a[l];
  default:;
  }
}

(and note that if we follow the C99 rules, which I think is the sensible thing
for the C++ front end to do, the same applies for identifiers of variably
modified type, e.g. int (*a)[l], not just VLAs: cases where the temporary
variable with the array size might not get initialized are all covered, not just
cases where memory for a VLA might not be allocated).

-- 
           Summary: Jumps into VLA or VM scope not rejected for C++
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jsm28 at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2005-04-19 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 21:20 jsm28 at gcc dot gnu dot org [this message]
2005-04-19 21:57 ` [Bug c++/21113] " pinskia at gcc dot gnu dot org
2005-05-01 11:32 ` jsm28 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=20050419212056.21113.jsm28@gcc.gnu.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).