[Tinyos Core WG] 2.1 release plans

[John Regehr]

In case anyone's curious these temp variables are used to say to Deputy: 
"Here's some bounds information and by the way it is clearly not aliased 
so don't worry about someone smashing it behind our back."

The idiom is very similar to the one commonly used in performance 
sensitive code where a temporary is introduced to facilitate 
optimizations when the compiler can't infer freedom from aliases on its own.

If Deputy were a bit smarter about pointers the need for some of these 
would go away.  However it's not obviously just a small matter of 
implementation to add these smarts...

John




Branislav Kusy wrote:
> Philip Levis wrote:
>> We're not at the point of code testing yet, but since we have a few  
>> people who are new to the release process, I thought I'd sketch how it  
>> works.
> 
> what versions of tools should we use for testing?
> 
> i was using nescc 1.2.8a and after i updated cvs today, it started 
> throwing bunch of warnings in the radiostack code (commited by john) 
> about unused tmpLen variable (COUNT macro is defined empty for nescc 
> version <1.3).
> 
> brano
> 
> 
> 
> _______________________________________________
> Tinyos-2.0wg mailing list
> Tinyos-2.0wg at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg
>