Re: NutEnterCritical vs NutEnterCriticalAccess()
Uwe Bonnes <bon-1JbLm1bU5j5ZIx36JBfelj3+ndqKAYMe9FMPySWZwLkb1SvskN2V4Q@public.gmane.org>
| Newsgroups | gmane.comp.hardware.microcontrollers.ethernut |
|---|---|
| Message-ID | <[email protected]> |
>>>>> "Nathan" == Nathan Moore <[email protected]> writes: Nathan> How about something like the following for each target cpu? Nathan> #define NutCriticalUpdate( VARIABLE, VALUE) \ do { \ size_t sz_ Nathan> = sizeof(typeof(VARIABLE)); \ size_t sza_ = Nathan> sizeof(sig_atomic_t); \ typeof(VARIABLE) * VP_ = &(VARIABLE); \ Nathan> typeof(VALUE) VAL_ = (VALUE); \ if (sz_ == sza_ && Nathan> is_alligned(VP_) { \ *VP_ = VAL_; \ } else if (sz_ < sza) { \ /* Nathan> special consideration for cpu */ \ } else { \ Nathan> NutEnterCritical(); \ *VP_ = VAL_; \ NutExitCritical(); \ } \ } Nathan> while (0) _______________________________________________ This sounds interesting however: - This is a GNU extention, and so deprecated for common code - This only on direction, for writing the variable and more code for reading the variable is needed. Bye -- Uwe Bonnes bon-1JbLm1bU5j5ZIx36JBfelj3+ndqKAYMe9FMPySWZwLkb1SvskN2V4Q@public.gmane.org Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 1623569 ------- Fax. 06151 1623305 --------- _______________________________________________ http://lists.egnite.de/mailman/listinfo/en-nut-discussion