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 middle-end/98508] Sanitizer disable -Wall and -Wextra Date: Tue, 05 Jan 2021 18:46:48 +0000 [thread overview] Message-ID: <bug-98508-4-9jJzAvZ7p8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98508-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98508 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |msebor at gcc dot gnu.org Component|c++ |middle-end Blocks| |24639 Last reconfirmed| |2021-01-05 --- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> --- It's possible (and obviously desirable) but difficult in general, which is why it hasn't been done yet. But in this case it shouldn't be hard: the warning is suppressed because the code finds the ASAN_MARK (UNPOISON, &s, 4); call in the IL below, and treats it like any other pass-by-reference call: it assumes that it might write to s and thus initialize it. The "fix" is simple: teach the warning that the .ASAN directive doesn't do that. int main () { int D.2825; { struct S s; try { .ASAN_MARK (UNPOISON, &s, 4); s = s; } finally { .ASAN_MARK (POISON, &s, 4); } } D.2825 = 0; return D.2825; } Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 [Bug 24639] [meta-bug] bug to track all Wuninitialized issues
next prev parent reply other threads:[~2021-01-05 18:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-04 8:31 [Bug c++/98508] New: " awdawdawdawq123123 at gmx dot de 2021-01-04 8:51 ` [Bug c++/98508] " jakub at gcc dot gnu.org 2021-01-04 8:59 ` awdawdawdawq123123 at gmx dot de 2021-01-05 18:46 ` msebor at gcc dot gnu.org [this message] 2021-01-05 19:00 ` [Bug middle-end/98508] " jakub at gcc dot gnu.org 2021-01-05 20:02 ` msebor at gcc dot gnu.org 2021-04-16 22:32 ` msebor 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-98508-4-9jJzAvZ7p8@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: linkBe 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).