public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/41874] Incorrect "dereferencing type-punned pointer will break strict-aliasing rules" warning
Date: Sat, 03 Dec 2022 22:03:23 +0000 [thread overview]
Message-ID: <bug-41874-4-Y2eoHqBYY9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41874-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41874
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |6.5.0
CC| |jason at gcc dot gnu.org
Known to work| |7.5.0
Target Milestone|--- |7.0
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #17 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Aso Renji from comment #15)
> No, this warning still appear if (and only if) you use -O2 or -O3
> optimization key (as it be in startpost with "g++ -O3 -Wstrict-aliasing
> test.cc -o /dev/null" line).
I don't see this with any compiler after 6.5.0.
next prev parent reply other threads:[~2022-12-03 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41874-4@http.gcc.gnu.org/bugzilla/>
2010-10-05 0:11 ` muravev at yandex dot ru
2010-10-05 4:49 ` fw at gcc dot gnu.org
2010-10-06 19:44 ` muravev at yandex dot ru
2010-10-06 20:57 ` rguenther at suse dot de
2012-10-15 9:27 ` paolo.carlini at oracle dot com
2012-10-15 9:45 ` rguenth at gcc dot gnu.org
2022-01-08 10:49 ` pinskia at gcc dot gnu.org
2022-12-03 22:03 ` jason at gcc dot gnu.org [this message]
2009-10-30 1:32 [Bug c++/41874] New: " jyasskin at gmail dot com
2009-11-06 9:09 ` [Bug c++/41874] " pinskia at gcc dot gnu dot org
2009-11-06 9:16 ` rguenther at suse dot de
2009-11-06 9:19 ` pinskia at gcc dot gnu dot org
2009-11-06 9:20 ` rguenth at gcc dot gnu dot org
2010-01-31 9:38 ` fw at deneb dot enyo dot de
2010-01-31 11:18 ` rguenth 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=bug-41874-4-Y2eoHqBYY9@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).