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: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- To: rth at redhat dot com
- Cc: gcc-patches at gcc dot gnu dot org, jakub at redhat dot com, dodji at redhat dot com, dnovillo at google dot com, davidxl at google dot com, wmi at google dot com
- Date: Wed, 14 Nov 2012 03:47:34 +0100
- Subject: Re: Committed: framework bits for disabling libsanitizer. RFC on which targets for which to disable it.
> From: Richard Henderson <rth@redhat.com>
> Date: Wed, 14 Nov 2012 02:34:32 +0100
> On 11/13/2012 05:20 PM, Hans-Peter Nilsson wrote:
> > Right. And, I think it's worth to repeat ;) that IMHO best to
> > there simply check that -faddress-sanitizer can compile
> > error-free (i.e. that TARGET_ASAN_SHADOW_OFFSET is defined on
> > the target). No target lists needed.
>
> We can't do that, since the compiler hasn't been built
> at top-level configure time. Obviously.
Yah, I was referring to configure-time in libsanitizer ...but
that's obviously not what you meant; I now see you referred to
toplevel configure.ac including various subdir/configure.tgt at
(toplevel) configure-time.
Delaying bail-out to target-library configure-time would
probably require things like a dummy buildsubdir/Makefile. I
don't see at a glance other libraries doing that so might not
be worth pursuing. Bah.
brgds, H-P