[En-Nut-Discussion] Fwd: Not fixed!!!: Re: confirmed!!! Re: NutOS 4.4.0 on ARM7: possibly bug in NutEnterCritical / NutExitCritical
Harald Kipp
harald.kipp at egnite.de
Wed Feb 27 09:33:06 CET 2008
Alain M. schrieb:
> So I believe that there are two alternatives left:
>
> a) use a global variable. This will be a lot slower due to ARM's
> pipeline architecture.
>
> b) Call NutEnterCritical/NutExitCritical obsolete, create a new with a
> parameter for the storage variable. But *replace* *only* the few ones
> that do have a problem with stack, wich I believe are few.
Why not do both?
a) Use a global variable to fix the existing NutEnterCritical /
NutExitCritical and declare it obsolete.
b) Create new macros with a parameter and replace the old one in all
Nut/OS libraries.
Harald
More information about the En-Nut-Discussion
mailing list