[PATCH v3] coverage : Add support to run coverage in supported bsp without extra options

Vijay Kumar Banerjee vijaykumar9597 at gmail.com
Wed Jul 11 05:11:00 UTC 2018


On 11 July 2018 at 02:49, Chris Johns <chrisj at rtems.org> wrote:

> On 11/7/18 3:18 am, Vijay Kumar Banerjee wrote:
> > On 10 July 2018 at 20:47, Gedare Bloom <gedare at rtems.org
> > <mailto:gedare at rtems.org>> wrote:
> >
> >     I don't see any problem with it, but I prefer to let Chris decide on
> merging...
> >
> > Thank you for the feedback :)
> >
>
> Sorry for the delay in responding.
>
> I suggest you leave the option as `--coverage` and consider looking at the
> `--debug-trace` option as a way to handle sets, for example
> `--coverage="sets:xyz,abc",report=gcov`.
>
> That's a good idea!
So we leave it for now and make a sub option when we have another report
format (gcov).

> The idea is to provide a single option we can add suboption parts.
>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180711/e0abe821/attachment-0002.html>


More information about the devel mailing list