Re: [avr-gcc-list] Re: AVR bug fix status

2008-03-19 Thread Mike Stein
Hi Andy, I'm happy to regression-test any gcc patches, if they are send to me as a MIME-attachment. They should be relative to the main gcc-directory. ___ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-gcc

Re: [avr-gcc-list] Re: AVR bug fix status

2008-03-17 Thread Andy H
Also we need volunteer to run patches for regressions 1) AVR target - I just do execute/torture 2) 686 target - so that proof looks better on primary target I only have CYGWIN - which is way too slow for testsuite - I think it takes 2/3 hours for just torture/execute and it would not be better

[avr-gcc-list] Re: AVR bug fix status

2008-03-16 Thread Andrew Hutchinson
I don't have any problem. I posted list so as not to forget which I had fixed and posted But I cant fix much more unless HEAD catches up. Some of the bug are same - I found some duplicates but suspect there are more. I have more fixs than I have posted in the email - but these need other pro

[avr-gcc-list] RE: AVR bug fix status

2008-03-16 Thread Weddington, Eric
Hi Andy, I understand your reluctance against 4.3.0. My problem is that I need to have support for the new xmega devices. All of that support has been written for 4.3.0, so I will be releasing the next WinAVR with 4.3.0. I have your patch for bugs #19636,24894,31644,31786: spill failure ICE. I ha