Re: [avr-libc-dev] [bug #22878] eeprom_*_word/dword/block cause hang in ATmega256x

2008-04-09 Thread Dmitry K.
Hm... Is avr-gcc for avr6 ready to use? I have try avr-gcc 4.4-20080404 (4.3.0 does not support avr6) with binutils 2.18. In result the small program without any EEPROM usage and without any inline functions gives incorrect code: /* avr-gcc 4.4-20080404 + binutils 2.18 produce incorrect code:

RE: [avr-libc-dev] [bug #22878] eeprom_*_word/dword/block cause hangin ATmega256x

2008-04-09 Thread Weddington, Eric
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org] On Behalf Of Dmitry K. Sent: Wednesday, April 09, 2008 12:24 AM To: avr-libc-dev@nongnu.org Subject: Re: [avr-libc-dev] [bug #22878] eeprom_*_word/dword/block cause hangin ATmega256x Hm... Is

RE: [avr-libc-dev] [bug #22878] eeprom_*_word/dword/block cause hangin ATmega256x

2008-04-09 Thread Stu Bell
Is avr-gcc for avr6 ready to use? Yes, with warnings. Since gcc insists on the size of a function pointer to be 2 bytes, anything using function pointers must be used with caution. If the function resides in the lower half of flash, the 2 byte pointer works fine. The problem is when the

RE: [avr-libc-dev] [bug #22878] eeprom_*_word/dword/block causehanginATmega256x

2008-04-09 Thread Weddington, Eric
Standard attachment error with Savannah's mailing lists. Trying again. Eric -Original Message- From: Stu Bell [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 09, 2008 11:40 AM To: Weddington, Eric; Dmitry K.; avr-libc-dev@nongnu.org Subject: RE: [avr-libc-dev] [bug #22878]

RE: [avr-libc-dev] [bug #22878] eeprom_*_word/dword/blockcausehanginATmega256x

2008-04-09 Thread Weddington, Eric
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org] On Behalf Of Weddington, Eric Sent: Wednesday, April 09, 2008 1:46 PM To: Stu Bell; Dmitry K.; avr-libc-dev@nongnu.org Subject: RE: [avr-libc-dev] [bug #22878]

Re: [avr-libc-dev] [bug #22878] eeprom_*_word/dword/block cause hangin ATmega256x

2008-04-09 Thread Dmitry K.
On Thursday 10 April 2008 01:15, Stu Bell wrote: Is avr-gcc for avr6 ready to use? Yes, with warnings. Since gcc insists on the size of a function pointer to be 2 bytes, anything using function pointers must be used with caution. If the function resides in the lower half of flash, the 2

Re: [avr-libc-dev] [bug #22878] eeprom_*_word/dword/blockcausehanginATmega256x

2008-04-09 Thread Dmitry K.
On Thursday 10 April 2008 08:19, Dmitry K. wrote: Yes, I have obtain the same result of compilation. Incorrect is result of linking (avr-objdump -d): ldi r24, 0 ldi r25, 0 in case of foo4() only. The trampoline stub for foo4() was created correctly. Now I have look again

Re: [avr-libc-dev] [bug #22878] eeprom_*_word/dword/block causehangin ATmega256x

2008-04-09 Thread Dmitry K.
On Thursday 10 April 2008 08:55, Weddington, Eric wrote: As the AVR Binutils port is not maintaned, IMHO, Dmitry, I have write-after-approval privs on binutils. You can send me a patch for binutils. Eric Good point. Thanks, Dmitry. ___

Re: [avr-libc-dev] [bug #22878] eeprom_*_word/dword/block causehanginATmega256x

2008-04-09 Thread Erik Christiansen
On Wed, Apr 09, 2008 at 01:38:54PM -0600, Stu Bell wrote: I'm not sure I should respond to this, as I'm not sure what the asm directive .rept 3 does. Having not seen anyone stop to provide an explanation, here's one. .rept 3 nop .endr merely plonks 30,000 NOPs into the