public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Konstantin Serebryany <konstantin.s.serebryany@gmail.com>
To: Jack Howarth <howarth@bromo.med.uc.edu>
Cc: Alexander Potapenko <glider@google.com>,
	Mike Stump <mikestump@comcast.net>,
		"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Wei Mi <wmi@google.com>, 	Dodji Seketeli <dodji@redhat.com>,
	iain@codesourcery.com
Subject: Re: [PATCh][Revisedx2] Fix PR55521 by switching libsanitizer from mach_overrideto mac interpose functions on darwin
Date: Tue, 04 Dec 2012 15:10:00 -0000	[thread overview]
Message-ID: <CAGQ9bdzREtd3nLrFOw51t2XmnkQ4MGqB6k85LYg2rfU7NuyjRw@mail.gmail.com> (raw)
In-Reply-To: <20121204150307.GA9473@bromo.med.uc.edu>

On Tue, Dec 4, 2012 at 7:03 PM, Jack Howarth <howarth@bromo.med.uc.edu> wrote:
> On Tue, Dec 04, 2012 at 11:02:01AM +0400, Konstantin Serebryany wrote:
>> r194120.
>> I've tested it on Linux, but not on Mac.
>
> kcc,
>    Tested at r194135 on x86_64-apple-darwin12. Thanks for the commit.
>            Jack
> ps Since clang in svn trunk has already switched to the mac function imposition version of asan,

did it?

> it might be time to deprecate mach_override out of llvm's compiler-rt trunk so
> lib/interception/mach_override/, lib/interception/interception_mac.cc and
> lib/interception/interception_mac.h could be removed.
>>
>> On Tue, Dec 4, 2012 at 6:44 AM, Alexander Potapenko <glider@google.com> wrote:
>> > I've added MISSING_BLOCKS_SUPPORT to LLVM compiler-rt in r169206.
>> > The rest of your change looks good to me as well.
>> >
>> > On Mon, Dec 3, 2012 at 6:33 PM, Alexander Potapenko <glider@google.com> wrote:
>> >> Jack,
>> >>
>> >> Note that MAC_INTERPOSE_FUNCTIONS is always defined in interception.h
>> >> to either 0 or 1.
>> >> I'm going to keep "#if MAC_INTERPOSE_FUNCTIONS" (adding "&&
>> >> !defined(MISSING_BLOCKS_SUPPORT)
>> >> " where appropriate) in libsanitizer.
>> >>
>> >> On Mon, Dec 3, 2012 at 11:17 AM, Mike Stump <mikestump@comcast.net> wrote:
>> >>> On Dec 3, 2012, at 8:02 AM, Jack Howarth <howarth@bromo.med.uc.edu> wrote:
>> >>>>   The attached patch eliminates PR 55521/sanitizer by switching libasan on darwin
>> >>>> from using mach_override to mac function interposition
>> >>>
>> >>> So, I'm thinking the sanitizer people will just review and approve it, even though it says darwin and is heavily darwin specific…  It's ok by me.
>> >>
>> >>
>> >>
>> >> --
>> >> Alexander Potapenko
>> >> Software Engineer
>> >> Google Moscow
>> >
>> >
>> >
>> > --
>> > Alexander Potapenko
>> > Software Engineer
>> > Google Moscow

  reply	other threads:[~2012-12-04 15:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 16:03 Jack Howarth
2012-12-03 19:17 ` Mike Stump
2012-12-04  2:34   ` Alexander Potapenko
2012-12-04  2:44     ` Alexander Potapenko
2012-12-04  7:02       ` Konstantin Serebryany
2012-12-04 15:03         ` Jack Howarth
2012-12-04 15:10           ` Konstantin Serebryany [this message]
2012-12-04 15:24             ` Jack Howarth
2012-12-04 16:06               ` Alexander Potapenko

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=CAGQ9bdzREtd3nLrFOw51t2XmnkQ4MGqB6k85LYg2rfU7NuyjRw@mail.gmail.com \
    --to=konstantin.s.serebryany@gmail.com \
    --cc=dodji@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=glider@google.com \
    --cc=howarth@bromo.med.uc.edu \
    --cc=iain@codesourcery.com \
    --cc=mikestump@comcast.net \
    --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).