Hello David,
I also would like to use GCC to get code coverage on an embedded system.
My approach would be to place the gcov information in a dedicated linker
set:
https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559004.html
Please have a look at the attached patches for a proposal to
On 11/20/19 4:14 PM, David Taylor wrote:
Sorry for not responding sooner.
Thanks Martin.
Like Joel we have a third party solution to instrumentation. Part of
my objection to the third party solution is freedom. There are
customizations we would like, but not having source we're at the mercy
o
Sorry for not responding sooner.
Thanks Martin.
Like Joel we have a third party solution to instrumentation. Part of
my objection to the third party solution is freedom. There are
customizations we would like, but not having source we're at the mercy
of the vendor both for whether it gets done
On 11/4/19 2:06 PM, david.tay...@dell.com wrote:
From: Martin Liška
Sent: Monday, November 4, 2019 4:20 AM
To: taylor, david; gcc@gcc.gnu.org
Subject: Re: GCC's instrumentation and the target environment
On 11/1/19 7:13 PM, David Taylor wrote:
Hello.
Hello.
What I'd like i
On Mon, Nov 4, 2019 at 7:06 AM wrote:
> > From: Martin Liška
> > Sent: Monday, November 4, 2019 4:20 AM
> > To: taylor, david; gcc@gcc.gnu.org
> > Subject: Re: GCC's instrumentation and the target environment
>
> > On 11/1/19 7:13 PM, David Taylor wrote:
&g
> From: Martin Liška
> Sent: Monday, November 4, 2019 4:20 AM
> To: taylor, david; gcc@gcc.gnu.org
> Subject: Re: GCC's instrumentation and the target environment
> On 11/1/19 7:13 PM, David Taylor wrote:
> Hello.
Hello.
> > What I'd like is a stable API
On 11/1/19 7:13 PM, David Taylor wrote:
I wish to use GCC based instrumentation on an embedded target. And I
am finding that GCC's libgcov.a is not well suited to my needs.
Ideally, all the application entry points and everthing that knows
about the internals of the implementation would be in s
I wish to use GCC based instrumentation on an embedded target. And I
am finding that GCC's libgcov.a is not well suited to my needs.
Ideally, all the application entry points and everthing that knows
about the internals of the implementation would be in separate files
from everything that does i/
