public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ygribov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/62089] Sanitizer may fail to instrument struct accesses Date: Thu, 16 Oct 2014 13:53:00 -0000 [thread overview] Message-ID: <bug-62089-4-ucXn6dztuX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62089-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62089 --- Comment #4 from ygribov at gcc dot gnu.org --- Author: ygribov Date: Thu Oct 16 13:52:45 2014 New Revision: 216331 URL: https://gcc.gnu.org/viewcvs?rev=216331&root=gcc&view=rev Log: 2014-10-16 Yury Gribov <y.gribov@samsung.com> Backport from mainline 2014-08-18 Yury Gribov <y.gribov@samsung.com> PR sanitizer/62089 * asan.c (instrument_derefs): Fix bitfield check. * c-c++-common/asan/pr62089.c: New test. * c-c++-common/asan/bitfield-1.c: New test. * c-c++-common/asan/bitfield-2.c: New test. * c-c++-common/asan/bitfield-3.c: New test. * c-c++-common/asan/bitfield-4.c: New test. Backport from mainline 2014-08-28 Yury Gribov <y.gribov@samsung.com> * c-c++-common/asan/pr62089.c: Fix test on 32-bit platforms. Added: branches/gcc-4_9-branch/gcc/testsuite/c-c++-common/asan/bitfield-1.c branches/gcc-4_9-branch/gcc/testsuite/c-c++-common/asan/bitfield-2.c branches/gcc-4_9-branch/gcc/testsuite/c-c++-common/asan/bitfield-3.c branches/gcc-4_9-branch/gcc/testsuite/c-c++-common/asan/bitfield-4.c branches/gcc-4_9-branch/gcc/testsuite/c-c++-common/asan/pr62089.c Modified: branches/gcc-4_9-branch/gcc/ChangeLog branches/gcc-4_9-branch/gcc/asan.c branches/gcc-4_9-branch/gcc/testsuite/ChangeLog
prev parent reply other threads:[~2014-10-16 13:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-62089-4@http.gcc.gnu.org/bugzilla/> 2014-08-11 14:24 ` y.gribov at samsung dot com 2014-08-18 8:24 ` ygribov at gcc dot gnu.org 2014-08-19 11:42 ` y.gribov at samsung dot com 2014-10-16 13:53 ` ygribov 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-62089-4-ucXn6dztuX@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).