public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/115096] -fstrict-aliasing miscompilation or missing warning
Date: Tue, 14 May 2024 21:57:24 +0000 [thread overview]
Message-ID: <bug-115096-4-uYmt4vVFWu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115096-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115096
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> the warning described in that bug is not occurring.
That is because in that case it had literally `(unsigned char**)&var` while in
this case it is spread across function calls and that would require a lot of
work to get the warning happening.
Note there are a few open bug reports specifically asking for a runtime
catching of this too; but that is also hard as you need to record the aliasing
set of when stores and loads happen.
next prev parent reply other threads:[~2024-05-14 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 21:25 [Bug c/115096] New: " Philip.Taff at itron dot com
2024-05-14 21:54 ` [Bug c/115096] " pinskia at gcc dot gnu.org
2024-05-14 21:57 ` pinskia at gcc dot gnu.org [this message]
2024-06-11 15:29 ` pinskia 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-115096-4-uYmt4vVFWu@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).