public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10538: gcc 3.2.3 does not issue a warning for "int a = a + 1" statements
Date: Tue, 29 Apr 2003 14:36:00 -0000	[thread overview]
Message-ID: <20030429143601.14614.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Remo Inverardi <invi@your.toilet.ch>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/10538: gcc 3.2.3 does not issue a warning for "int a = a +
 1" statements
Date: Tue, 29 Apr 2003 09:32:28 -0500 (CDT)

 > I just gave the current GCC documentation a second look, but I was not 
 > able to identify the extension your referring to (?) ...
 
 Maybe you're right. I tried to locate it in the manual some time ago and 
 couldn't find it either, after it had been discussed on the mailing lists 
 for the umpteenth time. It's documented in the mailing list archives, but 
 that is not a very good place...
 
 > what's more, I 
 > just tried compiling the same code with -ansi, -pedantic, and -Wall 
 > options, neither of which gave me a warning ...
 
 That's why I didn't close the report. 
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-04-29 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 14:36 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-29 14:16 bangerth
2003-04-29 14:06 invi

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=20030429143601.14614.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.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).