Even marginally smaller code size is very attractive (or essential) when we start running blip+rpl+coap.
- om_p On Tue, Jun 7, 2011 at 2:10 PM, Stephen Dawson-Haggerty <[email protected]> wrote: > I haven't seen any recent discussion about moving to mspgcc4 for 2.1.2, but > I know people are using it and it has significantly better support for > upcoming msp revisions. My question is if this is something we can shift to > recommending for the release, since it generates 5-10% smaller code with > more coming down the line, and the tree currently is known to work with it > at least on telosb and epic. > > Perhaps we could "recommend" mspgcc4 (some specific version which we decide) > and "deprecate" 3.2.3 for this release, but still test with both compilers > with the expectation we will move to the newer one only for future releases? > Steve > -- > stephen dawson-haggerty > http://cs.berkeley.edu/~stevedh > uc berkeley wireless and embedded systems lab > berkeley, ca 94720 > > _______________________________________________ > Tinyos-devel mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel > > _______________________________________________ Tinyos-devel mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
