This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH RFC: More control over which functions are instrumented


On 01 Aug 2007 14:49:32 -0700, Ian Lance Taylor <iant@google.com> wrote:
> -finstrument-functions-exclude-function-list is there because it seems
> odd to not have it, but the more commonly used option will be
> -finstrument-functions-exclude-file-list.  Note that files are matched
> as substrings, so you can say
> -finstrument-functions-exclude-file-list=include/c++ to exclude any
> function defined in a file in ...include/c++...

Ick, basing on where the function is defined seems like a hack.  That
is like the non NO_IMPLICIT_EXTERN_C problem.  Maybe I see this as
less useful than the instrument vs inline function issue.  You never
know people might have an include/c++ directory in their source tree
too which includes their C++ headers.  This one of the reasons why I
think it is less useful.

Thanks,
Andrew Pinski


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]