public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sirl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/64906] New: -fsanitize=integer-divide-by-zero creates false -Wmaybe-uninitialized warning Date: Mon, 02 Feb 2015 18:25:00 -0000 [thread overview] Message-ID: <bug-64906-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64906 Bug ID: 64906 Summary: -fsanitize=integer-divide-by-zero creates false -Wmaybe-uninitialized warning Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: sirl at gcc dot gnu.org CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org This testcase produces a false warning when compiled with -O2 -fsanitize=integer-divide-by-zero -Wmaybe-uninitialized: struct s { __SIZE_TYPE__ size; unsigned int flags; }; int testf(struct s * source) { __SIZE_TYPE__ msize = 0; if ((source->flags & 88) ? (__SIZE_TYPE__) 43 * 8 : 0) msize = source->size / ((source->flags & 88) ? (__SIZE_TYPE__) 43 * 8: 0); return msize; } test.c: In function 'testf': test.c:11:8: warning: 'iftmp.1' may be used uninitialized in this function [-Wmaybe-uninitialized] msize = source->size / ((source->flags & 88) ? (__SIZE_TYPE__) 43 * 8: 0); ^
next reply other threads:[~2015-02-02 18:25 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-02 18:25 sirl at gcc dot gnu.org [this message] 2015-09-21 13:52 ` [Bug sanitizer/64906] " mpolacek at gcc dot gnu.org 2015-09-22 13:21 ` mpolacek at gcc dot gnu.org 2015-09-22 14:06 ` mpolacek at gcc dot gnu.org 2015-09-25 9:51 ` mpolacek at gcc dot gnu.org 2015-09-25 10:46 ` mpolacek at gcc dot gnu.org 2015-09-25 10:47 ` mpolacek 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-64906-4@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).