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

[Bernard Fouché]

Bug 16884 is a real pain: I just spent hours figuring why something like
that would
break:

f()
{
  char s[2];

  s[1]=0;

  <.. loop filling s[0] with a char and doing a strcat(dest,s) ..>
}

Thanks for reporting this bug summary otherwise I would still be stuck.

-----Message d'origine-----
De : address@hidden
[mailto:address@hidden la part de Bob Paddock
Envoyé : mardi 31 août 2004 02:45
À : address@hidden
Objet : Re: [avr-gcc-list] Re: AVR toolset bugs and patches pending



> 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?

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.

--
                          http://www.softwaresafety.net/
 http://www.unusualresearch.com/ http://www.bpaddock.com/




_______________________________________________
avr-gcc-list mailing list
address@hidden
http://www.avr1.org/mailman/listinfo/avr-gcc-list