public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/83028] Incorrect -Wsequence-point warning in correct C++17 code with new evaluation order rules
Date: Mon, 13 Apr 2020 21:00:56 +0000 [thread overview]
Message-ID: <bug-83028-4-ts8AJsAbOz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-83028-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83028
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
Last reconfirmed| |2020-04-13
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed. Unless the C++ 2a standard defines behavior in all cases issuing
the warning for both valid (in C++ 2a) and invalid code code on the bases that
it's invalid in some other standard or language, and without distinguishing
between the valid uses from the invalid ones, would make the warning
meaningless. At a minimum, the warning should be split into two: one for
portability to other standards/languages, and another for problems in C++ 2a.
next parent reply other threads:[~2020-04-13 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-83028-4@http.gcc.gnu.org/bugzilla/>
2020-04-13 21:00 ` msebor at gcc dot gnu.org [this message]
2020-05-15 15:36 ` rafael at espindo dot la
2023-09-06 6:19 ` gayathri.gottumukkala.27 at gmail dot com
2023-09-06 13:46 ` redi 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-83028-4-ts8AJsAbOz@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).