public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/67258] "invalid vptr" false positive from ubsan for virtual inheritance
Date: Wed, 09 Sep 2015 16:35:00 -0000	[thread overview]
Message-ID: <bug-67258-4-ZelWcHBMMV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67258-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67258

--- Comment #3 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Author: trippels
Date: Wed Sep  9 16:34:59 2015
New Revision: 227591

URL: https://gcc.gnu.org/viewcvs?rev=227591&root=gcc&view=rev
Log:
Fix sanitizer/67258 by cherry picking upstream patch

        PR sanitizer/67258
        * ubsan/ubsan_type_hash.cc: Cherry pick upstream r244101.

Upstraem patch:
commit 1d2477faafda9ad2cc19927b3c31efd22747f013
Author: Alexey Samsonov <vonosmas@gmail.com>
Date:   Wed Aug 5 19:35:46 2015 +0000

    [UBSan] Fix UBSan-vptr false positive.

    Offset from vptr to the start of most-derived object can actually
    be positive in some virtual base class vtables.

    Patch by Stephan Bergmann!

    git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@244101
91177308-0d34-0410-b5e6-96231b3b80d8

Added:
    trunk/gcc/testsuite/g++.dg/ubsan/vptr-10.C
Modified:
    trunk/libsanitizer/ChangeLog
    trunk/libsanitizer/ubsan/ubsan_type_hash.cc


  parent reply	other threads:[~2015-09-09 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-67258-4@http.gcc.gnu.org/bugzilla/>
2015-09-01 18:33 ` avi@cloudius-systems.com
2015-09-09 13:53 ` trippels at gcc dot gnu.org
2015-09-09 16:35 ` trippels at gcc dot gnu.org [this message]
2015-09-09 16:40 ` trippels at gcc dot gnu.org
2015-09-09 16:43 ` trippels 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-67258-4-ZelWcHBMMV@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).