Sure makes sense.
On Fri, Nov 29, 2013 at 5:15 AM, Sebastian Huber <sebastian.hu...@embedded-brains.de> wrote: > It is not necessary to load the excecuting thread control again after > the context switch since it is an invariant of the executing thread. > --- > cpukit/score/src/threaddispatch.c | 3 +-- > 1 files changed, 1 insertions(+), 2 deletions(-) > > diff --git a/cpukit/score/src/threaddispatch.c > b/cpukit/score/src/threaddispatch.c > index 0c8298f..ecf6810 100644 > --- a/cpukit/score/src/threaddispatch.c > +++ b/cpukit/score/src/threaddispatch.c > @@ -156,12 +156,11 @@ void _Thread_Dispatch( void ) > #endif > > /* > - * We have to obtain these values again after the context switch since > the > + * We have to obtain this value again after the context switch since the > * heir thread may have migrated from another processor. Values from the > * stack or non-volatile registers reflect the old execution environment. > */ > per_cpu = _Per_CPU_Get(); > - executing = per_cpu->executing; > > #if !defined( RTEMS_SMP ) > _ISR_Disable( level ); > -- > 1.7.7 > > _______________________________________________ > rtems-devel mailing list > rtems-devel@rtems.org > http://www.rtems.org/mailman/listinfo/rtems-devel _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
