This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Committed: framework bits for disabling libsanitizer. RFC on which targets for which to disable it.
- From: Dodji Seketeli <dodji at redhat dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>, gcc-patches at gcc dot gnu dot org, Diego Novillo <dnovillo at google dot com>, Xinliang David Li <davidxl at google dot com>, Wei Mi <wmi at google dot com>
- Date: Tue, 13 Nov 2012 15:06:56 +0100
- Subject: Re: Committed: framework bits for disabling libsanitizer. RFC on which targets for which to disable it.
- References: <201211130138.qAD1cMWL013966@ignucius.se.axis.com> <874nktabgc.fsf@seketeli.org> <20121113132402.GX1886@tucnak.redhat.com>
Jakub Jelinek <jakub@redhat.com> writes:
> On Tue, Nov 13, 2012 at 02:17:55PM +0100, Dodji Seketeli wrote:
>> What do the maintainers think?
>
> Yes. And it shouldn't be just based on target CPU, but also based
> on target OS, I don't think libsanitizer supports anything but linux (glibc
> + maybe android) right now, with some smaller or bigger tweaks it could
> support darwin (but see the reports that it doesn't build there right now)
> or mingw/cygwin? (but there is a PR that it doesn't build there).
> So IMHO it should be a whitelist of supported targets with *) case
> adding noconfigdirs="$noconfigdirs target-libsanitizer", rather than
> blacklist of few unsupported ones. Can you please prepare a patch?
Sure, will do.
--
Dodji