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 c/66397] New: sanitize=undefined triggers extra -Warray-bounds warning Date: Wed, 03 Jun 2015 11:48:00 -0000 [thread overview] Message-ID: <bug-66397-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66397 Bug ID: 66397 Summary: sanitize=undefined triggers extra -Warray-bounds warning Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: sirl at gcc dot gnu.org Target Milestone: --- Created attachment 35691 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35691&action=edit testcase, warns with gcc-6 -c -O2 -fsanitize=undefined The attached testcase derived from a C++ iterator implementation relies on the fact that the undefined pCurrent-1 is immediately nullified again by the following pCurrent++ by the optimizer. But in current trunk r224064 the following warning is issued: test.c: In function 'test': test.c:19:53: warning: array subscript is below array bounds [-Warray-bounds] ths->pCurrent = (ths->pStart) ? ths->pStart - 1 : (stru *) 0; ^ Though the warning is not completely wrong, -Warray-bounds usually triggers only when the value is really accessed, or? gcc-5.1 compiles the testcase without warning.
next reply other threads:[~2015-06-03 11:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-03 11:48 sirl at gcc dot gnu.org [this message] 2015-06-03 11:56 ` [Bug c/66397] " pinskia at gcc dot gnu.org 2015-06-03 12:02 ` mpolacek at gcc dot gnu.org 2015-06-03 12:12 ` sirl at gcc dot gnu.org 2015-06-22 17:56 ` 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-66397-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).