public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/110368] Incorrect "is used uninitialized" warning message
Date: Sat, 07 Oct 2023 06:36:49 +0000 [thread overview]
Message-ID: <bug-110368-4-NCf4Z4w5nw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110368-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110368
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at gcc dot gnu.org
--- Comment #8 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Sam James from comment #7)
> That said, I suppose we should do better here with -Wstrict-aliasing. No
> level detects it.
I think it's very difficult to make -Wstrict-aliasing really useful. A
sanitizer at runtime would be much more useful but the develop of such a
sanitizer seems stalled
(https://discourse.llvm.org/t/reviving-typesanitizer-a-sanitizer-to-catch-type-based-aliasing-violations/).
For now we can only compare the output with or without -fno-strict-aliasing.
And we are already saying "try -fno-strict-aliasing" in the bug report
guidance.
prev parent reply other threads:[~2023-10-07 6:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 17:27 [Bug c/110368] New: " clugstj at gmail dot com
2023-06-22 17:29 ` [Bug c/110368] " clugstj at gmail dot com
2023-06-22 17:31 ` pinskia at gcc dot gnu.org
2023-06-22 17:32 ` pinskia at gcc dot gnu.org
2023-06-22 17:35 ` pinskia at gcc dot gnu.org
2023-06-22 17:37 ` pinskia at gcc dot gnu.org
2023-10-05 16:19 ` clugstj at gmail dot com
2023-10-06 15:51 ` sjames at gcc dot gnu.org
2023-10-07 6:36 ` xry111 at gcc dot gnu.org [this message]
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-110368-4-NCf4Z4w5nw@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).