public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jlegg at feralinteractive dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/65891] [9/10/11/12 Regression] -Wlogical-op now warns about logical ‘and’ of equal expressions even when different types/sizeofs are involved
Date: Wed, 23 Mar 2022 13:16:15 +0000 [thread overview]
Message-ID: <bug-65891-4-3tFchiizEm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65891-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65891
James Legg <jlegg at feralinteractive dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jlegg at feralinteractive dot com
--- Comment #7 from James Legg <jlegg at feralinteractive dot com> ---
(In reply to Kai Tietz from comment #3)
> For C++ delayed folding this issue won't be warned anymore, as for it sizeof
> isn't folded early.
With -fsanitize=integer-divide-by-zero, the spurious warning is still issued in
C++.
next prev parent reply other threads:[~2022-03-23 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 20:18 [Bug c/65891] New: " gerald at pfeifer dot com
2015-04-27 16:09 ` [Bug c/65891] " mpolacek at gcc dot gnu.org
2015-04-27 17:26 ` ktietz at gcc dot gnu.org
2022-01-03 20:10 ` [Bug c/65891] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-01-21 13:54 ` rguenth at gcc dot gnu.org
2022-03-23 13:16 ` jlegg at feralinteractive dot com [this message]
2022-05-27 9:35 ` [Bug c/65891] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug c/65891] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-07-19 12:57 ` [Bug c/65891] [12/13/14/15 " rguenth 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-65891-4-3tFchiizEm@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).