public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Konstantin Serebryany <konstantin.s.serebryany@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Jakub Jelinek <jakub@redhat.com>,
	       Dodji Seketeli <dodji@redhat.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	       Wei Mi <wmi@google.com>,
	Alexander Potapenko <glider@google.com>
Subject: Re: libsanitizer mege from upstream r171973
Date: Thu, 10 Jan 2013 15:38:00 -0000	[thread overview]
Message-ID: <20130110153803.GA7955@bromo.med.uc.edu> (raw)
In-Reply-To: <CAGQ9bdxfjWqRxBiictsbKQjvJ7Wz2qsSsgzbmoZyeMnZA48KZA@mail.gmail.com>

On Thu, Jan 10, 2013 at 11:01:30AM +0400, Konstantin Serebryany wrote:
> Hi,
> 
> The attached patch is the libsanitizer merge from upstream r171973.
> 
> Lots of changes. Among other things:
>   - slow CFI-based unwinder (off by default for now)
>   - more interceptors in asan (read, pread, etc)
>   - precise handling of memset/memcpy/etc (detects first overrun byte)
>   - new experimental asan allocator (off by default)
>   - asan now detects new/free, malloc/delete and new/delete[] mismatches
>   - tsan now detects more races IO operations
> 
> Patch for libsanitizer is automatically generated by libsanitizer/merge.sh
> Tested with
> rm -rf */{*/,}libsanitizer \
>   && make -j 50 \
>   && make -C gcc check-g{cc,++}
> RUNTESTFLAGS='--target_board=unix\{-m32,-m64\} asan.exp'
> 
> Our internal LLVM bots (Linux, Mac and Android) are also green, but
> since the changes are large something may potentially break on other
> platforms.
> 
> Ok to commit?
> 
> --kcc

kcc,
    Any chance that we can get http://llvm-reviews.chandlerc.com/D216 approved and committed
into llvm so that the libsanitizer merge can also eliminate the need for the Core Foundation
framework? It appears that you are assigned as the reviewer for that patch. Unfortunately
diff #518 has bit-rotted against current compiler-rt svn so Alexander will need to correct 
the patch for that.
              Jack

      parent reply	other threads:[~2013-01-10 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10  7:01 Konstantin Serebryany
     [not found] ` <CAGQ9bdzbtJ3Fh1QzgqzOvMaxzm98ZnyjORk+wU46Kbi0KWwCyA@mail.gmail.com>
2013-01-10  7:08   ` Konstantin Serebryany
2013-01-10 10:59     ` Jakub Jelinek
2013-01-10 11:28       ` Konstantin Serebryany
2013-01-10 11:31         ` Jakub Jelinek
2013-01-10 11:58           ` Konstantin Serebryany
2013-01-10 12:23             ` Jakub Jelinek
2013-01-10 12:28               ` Konstantin Serebryany
2013-01-10  7:09 ` Dmitry Vyukov
2013-01-10 15:38 ` Jack Howarth [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=20130110153803.GA7955@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --cc=dodji@redhat.com \
    --cc=dvyukov@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=glider@google.com \
    --cc=jakub@redhat.com \
    --cc=konstantin.s.serebryany@gmail.com \
    --cc=wmi@google.com \
    /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).