Identify control statements in source code

[Hermann Felbinger]

Joel Sherrill <joel.sherrill at oarcorp.com> schrieb am Fr., 14. Aug. 2015 um
04:26 Uhr:

>
>
> On August 13, 2015 7:15:08 PM CDT, Chris Johns <chrisj at rtems.org> wrote:
> >On 14/08/2015 6:34 am, Daniel Gutson wrote:
> >> I'd recommend a gcc plugin that generates your annotations;
> >
> >There is a Python framework for plugins to help make things easier ...
> >
> > http://gcc-python-plugin.readthedocs.org/en/latest/index.html
>
> I still don't understand the goal. I don't believe we have thoroughly
> integrated covoar with gcno and gcov yet. Until we do that and identify gcc
> issues, we shouldn't go down that path.
>
> Ok.
Due to explanations of gcov that can be found e.g. in
http://www.verifysoft.com/en_ctcpp_vs_gcov.html I thought it would be
beneficial for us, when we integrate a tool to analyze code coverage also
on the condition level.



> >Chris
> >_______________________________________________
> >devel mailing list
> >devel at rtems.org
> >http://lists.rtems.org/mailman/listinfo/devel
>
> --joel
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20150814/95e021ac/attachment-0002.html>