[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-libc-dev] Re: [avr-gcc-list] ATTiny2313 GCC Support? (fwd)

From: Bob Paddock
Subject: Re: [avr-libc-dev] Re: [avr-gcc-list] ATTiny2313 GCC Support? (fwd)
Date: Sun, 30 Jan 2005 09:41:56 -0500
User-agent: KMail/1.7.2

On Sunday 30 January 2005 08:53 am, Joerg Wunsch wrote:
> As Bob Paddock wrote:
> > "I think it is important to move attiny2313 and attiny13 from avr4
> > to avr2 first (at the same time in avr-libc, binutils and gcc), to
> > fix the recently reported bug (use of unsupported MUL instructions).
> > The fix is sub-optimal (MOVW not used, even though it is available),
> > but we probably can't do any better so close to the GCC 4.0
> > release..."
> This has been fixed long since (both in avr-libc, by me, and in GCC
> and binutils, by Marek), but you're right, the patch mentioned by Eric
> doesn't reflect that fix.
"E. Weddington"  wrote last Friday on the AVR-GCC list:

">As for the patches at:
>I have no idea if these are relevant at this point.

I just told you that you did need them.

Currently the only *released* project that has support for that device 
is avr-libc. Binutils and GCC do not have any *released* version that 
has support this device.

I would *strongly* suggest that you do not use GCC CVS HEAD for 
development as it is still highly unstable."

I'll conceded that avr-libc-1.2.1 is fixed, but if there is no released
version of GCC/Binutils with the patches applied, and it is not safe to use 
the unreleased version, and the patch set we have posted is broken, where 
does that leave us?  Rod and Victoria are examples of the broken patch set 
escaping into the real world.

Where do I get the patch set for GCC/Binutils that has the 'Tiny' fixed?

 http://www.unusualresearch.com/ http://www.bpaddock.com/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]