Re: [avr-gcc-list] Re: AVR toolset bugs and patches pending

[E. Weddington]

On 30 Aug 2004 at 20:45, Bob Paddock wrote:

> 
> > I also wanted to mention there are now 2 more confirmed AVR bugs that
> > generate wrong code (in the 3.4 series):
> >
> >     -16884
> >     <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16884>
> >
> >     - 16563
> >     <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16563>
> 
> Is there a list of bugs for 3.3.1?  Would it be safer for me to stay with 
> 3.3.1 till the 3.4/3.5 issues are sorted out?

Not an official list per se, though I'm keeping a personal list of known AVR 
bugs for GCC. 

Picking a version is always a personal choice; It's a matter of what is right 
for you. Having said 
that, so far I'm not jumping into 3.4.x because of some of the issues I've 
seen. IIRC, there is 
an "EEPROM ordering" issue.... I can't remember exactly what the problem is, 
something 
about it being reversed.... and nobody has filed a bug report that I know of.

 
> Here is a tip for anyone running WinAVR on XP.  XP using
> NTFS does support symbolic links.  In XP they are called
> 'junctions'.   If you do a 'dir' at the XP command prompt
> they show up as <JUNCTION> rather than <DIR>.
> 
> The program you need for creating junctions can be found here:
> http://www.sysinternals.com/ntw2k/source/misc.shtml#junction
> 
> My WinAVR directory is actually a Junction that I can point at
> either the 3.3.1 release or the 3.4.x release.  Makes it easy
> to keep multiple compilers on line with out (re)install issues.
> 

Nice setup. :-)

Eric