This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][Revised] Enable libsanitizer on darwin
- From: Dodji Seketeli <dodji at redhat dot com>
- To: Mike Stump <mikestump at comcast dot net>
- Cc: Jack Howarth <howarth at bromo dot med dot uc dot edu>, gcc-patches at gcc dot gnu dot org, wmi at google dot com, iain at codesourcery dot com, ro at CeBiTec dot Uni-Bielefeld dot DE, Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>
- Date: Thu, 15 Nov 2012 11:51:58 +0100
- Subject: Re: [PATCH][Revised] Enable libsanitizer on darwin
- References: <20121114144356.GA29142@bromo.med.uc.edu> <C4CBD0B3-5C90-41DA-8C28-B732C7D53CDE@comcast.net>
Maybe Konstantin could Help with the review, as this touches libsanitizer?
Cheers.
Mike Stump <mikestump@comcast.net> writes:
> On Nov 14, 2012, at 6:43 AM, Jack Howarth <howarth@bromo.med.uc.edu> wrote:
>> The attached patch assumes that mach_override/mach_override.h
>> and mach_override/mach_override.c has been imported by the libsanitizer
>> maintainers for use by darwin.
>
> So, the patches are a nice start. Since we are in stage3, they need
> to go in, in a way that is suitable for release. If the feature is
> expected to work (I think that's true) and if these patches don't yet
> work well enough (I don't have a take on wether this is the case or
> not), then as the patches go in, they need to go in with the feature
> off or disabled. So, I'd like a person that understand s libsanitizer
> and what we need (what is suitable) for release to approve the
> patches. If I do, I'd need to understand more than I do. What we
> don't want, a half implementation that is worse than saying,
> unsupported. I don't mind if the support isn't complete, yet, what is
> there works fine.
--
Dodji