RE: [avr-libc-dev] 1.6.2 release?

[Weddington, Eric]

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Dmitry K.
> Sent: Friday, March 28, 2008 11:40 PM
> To: address@hidden
> Subject: Re: [avr-libc-dev] 1.6.2 release?
> 
> On Friday 28 March 2008 13:48, Weddington, Eric wrote:
> [...]
> 
> > >   - how to use (void *)0 ?
> >
> > Could you explain? How would it be any different than it is now?
> I have check this.
> The Avr-gcc 4.2.3 and 4.3.0 have not any problems.
> The Avr-gcc 4.1.2 and early are too agressive in manipulations
> with 0 address (XMEGA's GPIO0 has address 0).

Good point. We'll have to keep an eye on this in the future.

> 
> > >   - predefined macroses
> >
> > Could you explain?
> What macroses must to use in source code?
> __AVR_XMEGA__ or '__AVR_ARCH__ > 100'?
> The 'common.h' uses '>= 100': what is arch 100 ?

Ah, I see. Architectures above 100 are currently XMEGA devices. I agree
that we will need to change this construct in the future to remove the
"magic numbers". But I think it is ok for this early stage.


> 
> > > The begin of Avr-libc TODO list:
> > >
> > > * Remove indirect access to common registers.
> >
> > True, that needs to be done. But IIRC, they're not really being used
> > right now anyway, so there is no harm right now.
> I have find:
>    Avr-libc 1.4: exp.S
>    Avr-libc 1.6: frexp.S (fixed now)
> It is needed to continue a check.

Thanks for checking.