Joel Sherrill schrieb am Fr., 14. Aug. 2015 um
04:26 Uhr:
>
>
> On August 13, 2015 7:15:08 PM CDT, Chris Johns 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
On August 13, 2015 7:15:08 PM CDT, Chris Johns 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
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
Chris
___
de
On August 13, 2015 5:38:24 PM CDT, Daniel Gutson
wrote:
>
>El 13/8/2015 19:35, "Joel Sherrill"
>escribió:
>>
>>
>>
>> On August 13, 2015 3:34:12 PM CDT, Daniel Gutson
> wrote:
>> >I'd recommend a gcc plugin that generates your annotations;
>otherwise,
>> >dig into gcov in order to parse a .gcn
El 13/8/2015 19:35, "Joel Sherrill" escribió:
>
>
>
> On August 13, 2015 3:34:12 PM CDT, Daniel Gutson <
daniel.gut...@tallertechnologies.com> wrote:
> >I'd recommend a gcc plugin that generates your annotations; otherwise,
> >dig into gcov in order to parse a .gcno file.
>
> Covoar already produc
On August 13, 2015 3:34:12 PM CDT, Daniel Gutson
wrote:
>I'd recommend a gcc plugin that generates your annotations; otherwise,
>dig into gcov in order to parse a .gcno file.
Covoar already produces gcov files. A previous gsoc student did that. This was
a bonus task and we were never 100% con
I'd recommend a gcc plugin that generates your annotations; otherwise,
dig into gcov in order to parse a .gcno file.
On Thu, Aug 13, 2015 at 5:09 PM, Hermann Felbinger
wrote:
> I am looking for something that processes the source code at compile time. I
> need this information to map branches fro
I am looking for something that processes the source code at compile time.
I need this information to map branches from execution traces to conditions
within the source code. With this information it will be possible to
analyze source coverage metrics as decision coverage or MCDC.
Daniel Gutson s
1) Are you looking for something statically processed (i.e. at compile
time) or at runtime? (such as gcov)
2) Are you looking for a way to add _your_ annotations, or a way to
_extract_ information?
In any case, the best way I can think of is with a gcc plugin.
Have you seen gcc's -ftest-coverage
On 8/13/2015 2:06 PM, Hermann Felbinger wrote:
Hi all!
I am working on a tool to analyze source code coverage for RTEMS.
Currently I am looking for a tool to annotate source code such that I can
extract information about statements and conditions that affect the control
flow of a program.
A
Hi all!
I am working on a tool to analyze source code coverage for RTEMS.
Currently I am looking for a tool to annotate source code such that I can
extract information about statements and conditions that affect the control
flow of a program.
A similar tool exists for Ada programs. They call this
11 matches
Mail list logo
