Re: [avr-gcc-list] Xmega support

2009-08-20 Thread Parthasaradhi Nayani
Hello All, Just not to enter a wrong address, I copy the address or clear the message and write new one. My apologies for inadvertently doing so. I am creating a new thread with a different heading. Thanks. Nayani --- On Thu, 8/20/09, David Kelly dke...@hiwaay.net wrote: From: David Kelly

[avr-gcc-list] XMEAG64 code problem

2009-08-20 Thread Parthasaradhi Nayani
Hello All, I am facing a peculiar problem with XMEGA64 code. When I use a global buffer in sprintf, the board appears to reset, but the initial values (which are changed before a call to sprintf) are not getting effected. If I use a local buffer (same size) there is no problem. Can some one

RE: [avr-gcc-list] XMEAG64 code problem

2009-08-20 Thread Weddington, Eric
-Original Message- From: avr-gcc-list-bounces+eric.weddington=atmel@nongnu.org [mailto:avr-gcc-list-bounces+eric.weddington=atmel@nongnu. org] On Behalf Of Parthasaradhi Nayani Sent: Thursday, August 20, 2009 12:34 AM To: avr-gcc-list@nongnu.org Subject: [avr-gcc-list]

[avr-gcc-list] char to int promotion in bitwise operators

2009-08-20 Thread Andrew Zabolotny
Hello! I've been looking at the compiled .S file for my library and have noticed that the code is substantially larger than could be because every my check for bitflags, like in this example: -- #define FLAG_A 0x01 #define FLAG_B 0x02 ... if (flags FLAG_A) ... if (flags

Re: [avr-gcc-list] char to int promotion in bitwise operators

2009-08-20 Thread Francisco Silva
2009/8/20 Andrew Zabolotny z...@homelink.ru: Hello! I've been looking at the compiled .S file for my library and have noticed that the code is substantially larger than could be because every my check for bitflags, like in this example: -- #define FLAG_A 0x01 #define