public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "leechung at 126 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67661] Wrong warning when declare VLAs: operation on 'x' may be undefined [-Wsequence-point]
Date: Thu, 24 Sep 2015 01:08:00 -0000 [thread overview]
Message-ID: <bug-67661-4-w4bFf5VwSA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67661-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67661
--- Comment #2 from leechung <leechung at 126 dot com> ---
(In reply to joseph@codesourcery.com from comment #1)
> You'll need to give a full testcase (complete compilable file and options
> used to compile it). What you gave isn't a compilable testcase; it gives
> "error: variably modified 'y' at file scope". Put inside a function, it
> gives "warning: unused variable 'y' [-Wunused-variable]", but does not
> give the warning you mention. And there's no variable 'b' in your example
> at all.
Sorry, I am less experience.
The following is the complete code:
#include <stdio.h>
int main (void)
{
int x = 0, y [++ x], z [++ x];
printf ("%d, %d, %d\n", sizeof x, sizeof y, sizeof z);
return 0;
}
and are compiled with option '-Wall'.for example:
gcc xx.c -Wall
then produce a warning 'operation on 'x' may be undefined [-Wsequence-point]'
next prev parent reply other threads:[~2015-09-24 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 6:19 [Bug c/67661] New: Wrong warning when declare VLAs: operation on 'b' " leechung at 126 dot com
2015-09-24 1:08 ` leechung at 126 dot com [this message]
2015-09-24 7:06 ` [Bug c/67661] Wrong warning when declare VLAs: operation on 'x' " manu at gcc dot gnu.org
2015-09-24 8:14 ` frankhb1989 at gmail dot com
2015-09-24 16:23 ` joseph at codesourcery dot com
2015-09-24 16:25 ` mpolacek at gcc dot gnu.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=bug-67661-4-w4bFf5VwSA@http.gcc.gnu.org/bugzilla/ \
--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).