On Tue, Jul 25, 2023 at 8:55 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 25.07.23 15:52, Joel Sherrill wrote:
> > Is something similar going to be needed for architecture and BSP
> > specific IDLE threads?
>
> You have to run gcov to figure this out. The GCC bug seems to t
On 25.07.23 15:52, Joel Sherrill wrote:
Is something similar going to be needed for architecture and BSP
specific IDLE threads?
You have to run gcov to figure this out. The GCC bug seems to trigger
only in very specific circumstances.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr.
Is something similar going to be needed for architecture and BSP specific
IDLE threads?
--joel
On Tue, Jul 25, 2023 at 1:09 AM Chris Johns wrote:
> OK
>
> Chris
>
> On 25/7/2023 4:04 pm, Sebastian Huber wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108658
> >
> > This GCC bug leads to
OK
Chris
On 25/7/2023 4:04 pm, Sebastian Huber wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108658
>
> This GCC bug leads to an incomplete code coverage status.
>
> Update #4932.
> ---
> cpukit/score/cpu/no_cpu/cpuidle.c | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108658
This GCC bug leads to an incomplete code coverage status.
Update #4932.
---
cpukit/score/cpu/no_cpu/cpuidle.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/cpukit/score/cpu/no_cpu/cpuidle.c
b/cpukit/score/cpu/no_cpu/cpuidle.c
inde
