[Tinyos Core WG] Deputy and Safe TinyOS warnings

[Kevin Klues]

which platform?

What is the error?

Are you using the 'cthreads' target instead of just 'threads'?

Kevin

On Wed, Jul 2, 2008 at 8:27 PM, John Regehr <regehr at cs.utah.edu> wrote:
> Ok: in CVS HEAD the tosthreads apps compile in safe mode now.  I tested
> Blink and Bounce on telosb and all looks good.
>
> I can't compile anything in capps, safe or unsafe.
>
> John
>
>
>
> David Gay wrote:
>> A quick perusal of warnings / errors:
>>
>> - the memset warning is a deputy bug
>> - the __deputy_memset error is not a deputy bug - we need to fix
>> tos/lib/safe/include/deputy/checks.h to define __deputy_memset
>> - the ConfigStorageP warnings are a deputy bug (but probably avoidable
>> by a small nesC change)
>> - the rv warning in TransformCounterC$0$get is a msp430-gcc bug - we
>> added an initialization in the TinyOS source code (see the declation
>> of rv in tos/lib/timer/TransformCounterC.nc) to work around this bug,
>> but deputy's optimizer removes this "useless" initialization ;-)
>> - the 0-size array warnings in
>> tos/lib/net/Deluge/FlashVolumeManager/FlashVolumeManagerP.nc are
>> "real" (those are 0-size arrays), but should ideally not be present as
>> that module is not marked @safe() (I'm not sure how fixable this is -
>> @safe() really only applies to functions, not to top-level
>> declarations)
>>
>> David
>> _______________________________________________
>> Tinyos-2.0wg mailing list
>> Tinyos-2.0wg at millennium.berkeley.edu
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg
>>
> _______________________________________________
> Tinyos-2.0wg mailing list
> Tinyos-2.0wg at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg
>



-- 
~Kevin