https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87442
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.0 |9.0
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
Ok, I've got a patch prototype and I hope I'll be able to sent it before
the end of this stage1.
> The idea is to add two options to easily include/exclude some files from
> being instrumented.
> Here are two use cases:
> 1) -coverage-exclude=/usr/include/*: typically we remove the data for such
> files when post-processing the gcno/gcda so we don't need to instrument them
> and so we could reduce the overhead due to instrumentation.
> 2) -coverage-filter=.*/foo.cpp:.*/bar.cpp: here we want to only instrument
> these two files (for example, to display code coverage data for files
> appearing in a patch at review phase)
However, calixte can you please explain me difference in between those two
options.
More precisely, one is a white list and the second one is a black list. Will
you
mix these together or they will be used exclusively?
