This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFC Asan instrumentation control
- From: Yury Gribov <y dot gribov at samsung dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Viacheslav Garbuzov <v dot garbuzov at samsung dot com>, Max Ostapenko <m dot ostapenko at partner dot samsung dot com>
- Date: Tue, 10 Dec 2013 13:31:22 +0400
- Subject: Re: RFC Asan instrumentation control
- Authentication-results: sourceware.org; auth=none
- References: <52A1B4F2 dot 8040105 at samsung dot com> <20131206120929 dot GJ892 at tucnak dot redhat dot com> <52A6CB9F dot 2000802 at samsung dot com> <20131210081046 dot GM892 at tucnak dot redhat dot com>
Jakub wrote:
> You can still -include some header file from the command line and put the
> attributes in there or similar.
True although this probably won't work with C++ methods.
> The blacklist is really terribly ugly hack,
> which can't work reliably. What do you do for anonymous namespaces? For
> not exported functions? Identifying externally decls by name is
> problematic, without mangled names very problematic, with mangled
names not
> useful for symbols that are local to the TU.
Good points, I guess the present blacklist format does not really
address them.
But I don't think that's a fundamental limitation - it should be
possible to cook a nice query language for C++.
Konstantin wrote:
> All of this is a bit ugly.
> But we have no other mechanism that works today.
Agreed. I guess our main question is whether such mechanism is really
needed by developers.
-Y