public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <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 07:06:00 -0000 [thread overview]
Message-ID: <bug-67661-4-UYhpquOGQC@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
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
int main (void)
{
int x = 0, y [++ x], z [++ x];
__builtin_printf ("%d, %d, %d\n", sizeof x, sizeof y, sizeof z);
return 0;
}
$ cc1 -Wsequence-point test.c
test.c:3:27: warning: operation on ‘x’ may be undefined [-Wsequence-point]
int x = 0, y [++ x], z [++ x];
^
I'll let someone else with more knowledge of the standard to decide if the
warning is correct or not.
>From gcc-bugs-return-497946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Sep 24 07:25:11 2015
Return-Path: <gcc-bugs-return-497946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34658 invoked by alias); 24 Sep 2015 07:25:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34598 invoked by uid 48); 24 Sep 2015 07:25:07 -0000
From: "mpolacek at gcc dot gnu.org" <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 07:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-67661-4-oOKeuKpGb4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67661-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg01924.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?idg661
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I think the warning is bogus and the code looks valid.
next prev parent reply other threads:[~2015-09-24 7:06 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 ` [Bug c/67661] Wrong warning when declare VLAs: operation on 'x' " leechung at 126 dot com
2015-09-24 7:06 ` manu at gcc dot gnu.org [this message]
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-UYhpquOGQC@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).