RE: [avr-gcc-list] wrong code from avr-gcc 4.1.2?

[John Regehr]

> Definitely, NOT stock FSF 4.3.0. The stock FSF 4.3.0 is broken for the
> AVR port (bad code generation), unless you have patches to fix it. 4.1.x
> or 4.2.x would be more conservative. IIRC, there are patches that I used
> to fix various bugs. A number of those patches have been committed but
> only on HEAD. Probably the most important thing is that you have bug-fix
> patches for the relative version that you're using. Both Andy Hutchinson
> and Anatoly Sokolov have been very active recently in getting a number
> of outstanding bugs fixed, so ideally you would want to use HEAD. ;-)
> But I undertand that it's very impractical. That's my 2 cents anyway.

Thanks Eric.

Yes I expect using HEAD is impractical-- compiler version thrash is a 
major headache for developers.

And just to be sure-- is the collection of patches here always the 
definitive one?

  http://winavr.cvs.sourceforge.net/winavr/patches/gcc/

I have been using the shell scripts from avrfreaks to build various 
avr-gccs, based on the assumption that those are derived from these 
patchsets.  (But as I said it's Kevin Klues who has put together the 
compiler packages for TinyOS-- I'm only peripherally involved with that 
process).

John