From: Konstantin Serebryany <konstantin.s.serebryany@gmail.com>
To: 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>
Subject: Re: libsanitizer mege from upstream r171973
Date: Thu, 10 Jan 2013 07:08:00 -0000 [thread overview]
Message-ID: <CAGQ9bdx9LW-GaLJz_1PEdsZ9v9LCeBpwv6R775dN1ha_raKMpQ@mail.gmail.com> (raw)
In-Reply-To: <CAGQ9bdzbtJ3Fh1QzgqzOvMaxzm98ZnyjORk+wU46Kbi0KWwCyA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
Sending gzip-ed patch (otherwise it's too large)
On Thu, Jan 10, 2013 at 11:04 AM, Konstantin Serebryany
<konstantin.s.serebryany@gmail.com> wrote:
> Actually attaching the patch.
>
> On Thu, Jan 10, 2013 at 11:01 AM, Konstantin Serebryany
> <konstantin.s.serebryany@gmail.com> 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
[-- Attachment #2: libsanitizer-171973.patch.gz --]
[-- Type: application/x-gzip, Size: 72125 bytes --]
next prev parent reply other threads:[~2013-01-10 7:08 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 [this message]
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
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=CAGQ9bdx9LW-GaLJz_1PEdsZ9v9LCeBpwv6R775dN1ha_raKMpQ@mail.gmail.com \
--to=konstantin.s.serebryany@gmail.com \
--cc=dodji@redhat.com \
--cc=dvyukov@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).