public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at igpm dot rwth-aachen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/17041] [3.5 regression] Erroneous "suggest parentheses around assignment used as truth value" warning in template members.
Date: Tue, 17 Aug 2004 15:31:00 -0000 [thread overview]
Message-ID: <20040817153112.21148.qmail@sourceware.org> (raw)
In-Reply-To: <20040815223820.17041.carlo@gcc.gnu.org>
------- Additional Comments From reichelt at igpm dot rwth-aachen dot de 2004-08-17 15:31 -------
Subject: Re: [3.5 regression] Erroneous
"suggest parentheses around assignment used as truth value" warning in
template members.
On 17 Aug, jsm at polyomino dot org dot uk wrote:
> I take it then that this works (i.e. doesn't warn) in 3.3.x or earlier,
> for it to be a regression? Since this warning was *completely* broken
> (i.e. never warning even when it should) in 3.4.x as it hadn't been
> reimplemented for the new parser.
All compilers from (at least) 2.95.3 up to and including 3.4.1 correctly
do not issue a warning for the testcase.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17041
next prev parent reply other threads:[~2004-08-17 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 22:38 [Bug c++/17041] New: [regression 3.5] " carlo at gcc dot gnu dot org
2004-08-15 22:54 ` [Bug c++/17041] [3.5 regression] " bangerth at dealii dot org
2004-08-16 17:37 ` pinskia at gcc dot gnu dot org
2004-08-17 15:00 ` reichelt at gcc dot gnu dot org
2004-08-17 15:25 ` jsm at polyomino dot org dot uk
2004-08-17 15:31 ` reichelt at igpm dot rwth-aachen dot de [this message]
2004-08-17 15:33 ` carlo at alinoe dot com
2004-08-17 18:23 ` jsm at polyomino dot org dot uk
2004-08-19 8:02 ` cvs-commit at gcc dot gnu dot org
2004-08-19 14:09 ` pinskia at gcc dot gnu dot 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=20040817153112.21148.qmail@sourceware.org \
--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).