[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avr-libc-dev] A possible workaround to bug #21872
From: |
Weddington, Eric |
Subject: |
RE: [avr-libc-dev] A possible workaround to bug #21872 |
Date: |
Tue, 22 Jan 2008 16:08:02 -0700 |
> -----Original Message-----
> From:
> address@hidden
> [mailto:address@hidden
> org] On Behalf Of Dmitry K.
> Sent: Tuesday, January 22, 2008 4:03 PM
> To: address@hidden
> Subject: [avr-libc-dev] A possible workaround to bug #21872
>
> Hi.
>
> Avr-libc bug #21872: __floatunsisf/undisf incorrectly named
>
> This bug is fixed at the end of 2007 in HEAD and 1.6
> branches.
>
> (Remember: It enlarges the program size approx. by 1kB. The
> reason is incorrect name of function unsigned_long_to_float
> conversion. So the libgcc's variant is used: large if flash
> and RAM. This bug is actual with new compiler - 4.2 - for
> all Avr-libc branches, including 1.4, 1.2 and so on.)
>
> This is actually to users who are not happy to load
> a corrected CVS Avr-libc version.
>
> The possible workaround is to add the needed function
> manualy like:
>
> extern float __floatunssisf (unsigned long u);
> float __floatunsisf (unsigned long u)
> {
> return __floatunssisf (u);
> }
>
> This is not the best method. This is the simplest
> to understand.
I would also like to do a new release of WinAVR in late February (next
month). At that time, I hope that we can release avr-libc 1.6.2, and
hopefully correct any issues like this.
Eric W.