From: Dodji Seketeli <dodji@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Dodji Seketeli <dseketel@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [asan] Fix some asan ICEs
Date: Mon, 03 Dec 2012 14:52:00 -0000 [thread overview]
Message-ID: <m3624j9oiq.fsf@redhat.com> (raw)
In-Reply-To: <20121127184028.GE2315@tucnak.redhat.com> (Jakub Jelinek's message of "Tue, 27 Nov 2012 19:40:28 +0100")
> Ok for trunk?
>
> 2012-11-27 Jakub Jelinek <jakub@redhat.com>
>
> * asan.c (instrument_mem_region_access): Don't instrument
> if base doesn't have pointer type or len integral type.
> Add cast if len doesn't have size_t compatible type.
> (instrument_builtin_call): Don't instrument BUILT_IN_ATOMIC_LOAD,
> BUILT_IN_ATOMIC_TEST_AND_SET, BUILT_IN_ATOMIC_CLEAR,
> BUILT_IN_ATOMIC_EXCHANGE, BUILT_IN_ATOMIC_COMPARE_EXCHANGE
> and BUILT_IN_ATOMIC_STORE.
This is OK. Thanks, and sorry for the delay.
--
Dodji
next prev parent reply other threads:[~2012-12-03 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 18:41 Jakub Jelinek
2012-12-03 14:52 ` Dodji Seketeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-18 13:33 Jakub Jelinek
2012-10-18 16:02 ` Xinliang David Li
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=m3624j9oiq.fsf@redhat.com \
--to=dodji@redhat.com \
--cc=dseketel@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).