public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/10143: Post increment doesn work more than once per statement
Date: Wed, 19 Mar 2003 20:16:00 -0000	[thread overview]
Message-ID: <20030319201601.27364.qmail@sources.redhat.com> (raw)

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

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Nick Macdonald <macdonn@nortelnetworks.com>
Cc: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>, 
     <gcc-gnats@gcc.gnu.org>,  <gcc-bugs@gcc.gnu.org>
Subject: Re: c/10143: Post increment doesn work more than once per statement
Date: Wed, 19 Mar 2003 20:09:49 +0000 (GMT)

 On Wed, 19 Mar 2003, Nick Macdonald wrote:
 
 > {macdonn}195: gcc -Wsequence-point WeirdForLoop.c
 > 
 > There is no sequence point warning when compiling either program... 
 > using either 2.95.2 or 3.2.2
 
 That then is a bug in -Wsequence-point we need to fix (and this PR should
 be reopened and retitled to reflect that): this is one of the simple cases
 that -Wsequence-point is meant to detect, not one of the complicated cases
 that are known not to be handled.
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 


             reply	other threads:[~2003-03-19 20:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 20:16 Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-20  0:16 Neil Booth
2003-03-19 22:36 Nick Macdonald
2003-03-19 19:56 Nick Macdonald
2003-03-19 19:06 Joseph S. Myers
2003-03-19 14:26 Falk Hueffner
2003-03-19 14:06 Nick Macdonald
2003-03-19  7:10 neil
2003-03-19  1:06 macdonn

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=20030319201601.27364.qmail@sources.redhat.com \
    --to=jsm28@cam.ac.uk \
    --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).