[RTEMS Project] #4196: Improve gcov support provided by GCC for RTEMS

[RTEMS trac]

#4196: Improve gcov support provided by GCC for RTEMS
-----------------------------+------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:  6.1
Component:  tool/gcc         |     Version:  6
 Severity:  normal           |  Resolution:  fixed
 Keywords:  qualification    |  Blocked By:
 Blocking:                   |
-----------------------------+------------------------------
Description changed by Sebastian Huber:

Old description:

> If we want to use gcov in RTEMS to get code coverage in all system
> states, then we need some tweaks in GCC:
>
> https://gcc.gnu.org/pipermail/gcc/2020-November/234164.html
>
> The linker set based gcov information registration is already included in
> GCC:
>
> https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-
> fprofile-info-section
>
> There is a discussion about how the gcov information can be transferred
> from the embedded system to the host:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559342.html
>
> The GCC integration needs to wait for the GCC 12 development start.

New description:

 If we want to use gcov in RTEMS to get code coverage in all system states,
 then we need some tweaks in GCC:

 https://gcc.gnu.org/pipermail/gcc/2020-November/234164.html

 The linker set based gcov information registration is already included in
 GCC:

 https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-
 fprofile-info-section

 There is a discussion about how the gcov information can be transferred
 from the embedded system to the host:

 https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559342.html

 The following patch set was integrated in GCC 13:

 https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593536.html

 https://gcc.gnu.org/onlinedocs/gcc/Freestanding-Environments.html
 #Freestanding-Environments

--

--
Ticket URL: <http://devel.rtems.org/ticket/4196#comment:9>
RTEMS Project <http://www.rtems.org/>
RTEMS Project