Re: [PATCH] score: Add workaround for GCC bug

2023-07-25 Thread Joel Sherrill 
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 trigger
> only in very specific circumstances.
>

OK. Just something to be aware of then.

Thanks.

--joel

>
> --
> embedded brains GmbH
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.hu...@embedded-brains.de
> phone: +49-89-18 94 741 - 16
> fax:   +49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] score: Add workaround for GCC bug

2023-07-25 Thread Sebastian Huber 

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. 4
82178 Puchheim
Germany
email: sebastian.hu...@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] score: Add workaround for GCC bug

2023-07-25 Thread Joel Sherrill 
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 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
> > index bff1309d39..a6001e73b0 100644
> > --- a/cpukit/score/cpu/no_cpu/cpuidle.c
> > +++ b/cpukit/score/cpu/no_cpu/cpuidle.c
> > @@ -33,6 +33,13 @@
> >
> >  void *_CPU_Thread_Idle_body( uintptr_t ignored )
> >  {
> > +  /*
> > +   * This is a workaround for:
> > +   *
> > +   * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108658
> > +   */
> > +  __asm__ volatile ("");
> > +
> >while ( true ) {
> >  /* Do nothing */
> >}
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] score: Add workaround for GCC bug

2023-07-25 Thread Chris Johns 
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/cpukit/score/cpu/no_cpu/cpuidle.c 
> b/cpukit/score/cpu/no_cpu/cpuidle.c
> index bff1309d39..a6001e73b0 100644
> --- a/cpukit/score/cpu/no_cpu/cpuidle.c
> +++ b/cpukit/score/cpu/no_cpu/cpuidle.c
> @@ -33,6 +33,13 @@
>  
>  void *_CPU_Thread_Idle_body( uintptr_t ignored )
>  {
> +  /*
> +   * This is a workaround for:
> +   *
> +   * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108658
> +   */
> +  __asm__ volatile ("");
> +
>while ( true ) {
>  /* Do nothing */
>}
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel