[avr-gcc-list] WINAVR with GCC 4.3.3

Hi, Can anybody tell me when WINAVR with GCC 4.3.3 will be available? There is serious bug with GCC 4.3.2 and which is fixed in 4.3.3 hence I need same to proceed with my project. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38342 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38342

RE: [avr-gcc-list] WINAVR with GCC 4.3.3

-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 Dushyant Sharma Sent: Friday, June 19, 2009 2:38 AM To: avr-gcc-list@nongnu.org Subject: [avr-gcc-list] WINAVR

Re: [avr-gcc-list] WINAVR with GCC 4.3.3

Hi, I have a project built around a Tiny26. It was compiled with WinAVR-20070525. I'd stuck to this version for a long time, until recently when I upgraded to 20090313. Soon after, I had to recompile my project due some change in specs. Imagine my shock when AVRstudio complained that the

Re: [avr-gcc-list] WINAVR with GCC 4.3.3

If that is true, then, by 2012, I'll have to redesign my current Tiny2313 / Tiny26 projects around a Mega128 :-)) !!! (lol) Funny, assembler doesn't have this problem... :) Check that you have optimization set properly, -O3 or -Os. I've seen cases where -O3 was smaller than -Os, but it's

[avr-gcc-list] Memory problem

Hello all, I have interfaced flash memory to my mega64 and created a section for this memory. I have some variables and two structures which are located in this memory. Initially I defined the variables first and then the structure. After linking I checked the map and list files and found that

Re: [avr-gcc-list] Memory problem

On Mon, Jun 22, 2009 at 10:17:50AM -0700, Parthasaradhi Nayani wrote: Hello all, I have interfaced flash memory to my mega64 and created a section for this memory. I have some variables and two structures which are located in this memory. Initially I defined the variables first and then the

RE: [avr-gcc-list] WINAVR with GCC 4.3.3

I have a project built around a Tiny26. [blah blah blah code bloat blah blah blah Imagine my shock blah blah blah redesign my current Tiny2313 / Tiny26 projects around a Mega128 blah blah blah] This is old news. Without going into the reasons why it happens, the following are some tips I

RE: [avr-gcc-list] WINAVR with GCC 4.3.3

I have spent a fair amount of time trying out various compiler options and this is what I settled on for large projects. A lot of suggested options made no significant difference in my projects however, your mileage may vary, so give em a try and see what happens: CFLAGS += -funsigned-bitfields