public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10790: g++/gcc
Date: Wed, 14 May 2003 19:16:00 -0000	[thread overview]
Message-ID: <20030514191600.20902.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10790; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: lgang@yahoo.com, "Gcc-Bugs@Gcc. Gnu. Org" <gcc-bugs@gcc.gnu.org>
Cc: Andrew Pinski <pinskia@physics.uc.edu>, gcc-gnats@gcc.gnu.org
Subject: Re: c++/10790: g++/gcc
Date: Wed, 14 May 2003 15:09:40 -0400

 This is a GCC extension so it is not a bug, use -pedantic or 
 -pedantic-errors to see that they are not accepted.
 I get some warnings or errors if -pedantic-errors:
 
 test2.cc: In function `int main()':
 test2.cc:7: warning: ISO C++ forbids variable-size array `arr'
 test2.cc:9: warning: ISO C++ forbids variable-size array `arr2'
 
 Thanks,
 Andrew Pinski
 
 PS can someone close this bug as it is not really a bug but a 
 misunderstanding of GCC extensions.
 
 
 On Wednesday, May 14, 2003, at 13:59 US/Eastern, lgang@yahoo.com wrote:
 
 >
 >> Number:         10790
 >> Category:       c++
 >> Synopsis:       g++/gcc
 >> Confidential:   no
 >> Severity:       serious
 >> Priority:       medium
 >> Responsible:    unassigned
 >> State:          open
 >> Class:          sw-bug
 >> Submitter-Id:   net
 >> Arrival-Date:   Wed May 14 18:06:00 UTC 2003
 >> Closed-Date:
 >> Last-Modified:
 >> Originator:     lgang@yahoo.com
 >> Release:        G++ 3.2
 >> Organization:
 >> Environment:
 > Solaris 8
 >> Description:
 > Should a non-constant array be allowed in C/C++? I guess not.  See the 
 > following code.
 >
 > int main()
 > {
 >   int c;
 >   scanf("%d", &c);
 >   int arr[c];
 >   int p;
 >   char arr2[c];
 >   int another;
 >   printf ("Terrible, diff=%d, diff=%d\n",
 > 			 (char*)&c-(char*)&p, (char*)&p - (char*)&another);
 >   return 0;
 > }
 >
 > Seems that compiler treats it int arr[c] as int *arr.  I don't think 
 > it should compile.
 >
 > Thanks
 >> How-To-Repeat:
 >
 >> Fix:
 >
 >> Release-Note:
 >> Audit-Trail:
 >> Unformatted:
 >
 >
 


             reply	other threads:[~2003-05-14 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 19:16 Andrew Pinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 21:02 bangerth
2003-05-14 18:06 lgang

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=20030514191600.20902.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --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: 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).