Electronics & Programming

develissimo

Open Source electronics development and programming

  • You are not logged in.

#1 March 16, 2008 18:56:45

Andrew H.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

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


I don't have any problem. I posted list so as not to forget which I hadfixed and postedBut I cant fix much more unless HEAD catches up. Some of the bug aresame - I found some duplicates but suspect there are more.I have more fixs than I have posted in the email - but these need otherproblems fixed before a patch would make sense.I posted response to GCC maintainer comment on same day. I will chasethem again.That bug was regression from 4.2 - but I cannot change its status.

Also many bugs are marked UNCONFIRMED - I cannot change status.

Having bug CONFIRMED and REGRESSION gets more attention.Beware, Combine bug is nasty - if you are lucky, it will cause SEGfault - if not bad code - no warning.We could do with a volunteer to create AVR testcase directory in GCC -so we could add testcases.It makes it easier to find potential duplicates.


Andy



Weddington, Eric wrote: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 have your patch for bugs #27192,35013: call through function pointer.
I am doing a test build now with your patch for bug #32871.
The patch for bug #34412 has been committed.

For bugs #34916,35519, IIRC there was a GCC maintainer that wasn't happy
about your proposed patch. So you'll either have to convince them that
it is ok, or rework your patch.

For the other bugs (27663,35542; 35507), these are missed optimizations.
They are important, but I would rather focus on getting your current
fixes committed as those are more important bugs to get fixed.

I do not have write permissions in GCC (I don't yet have the FSF
Copyright Assignment paperwork done), so I can't do a whole lot other
than use your patches in WinAVR. Anatoly is one of the AVR port
maintainers, so he will have to get these committed. I know that both
Anatoly and I have a number of patches in our backlog to get committed,
so I hope that we can get to your patches soon. I know that Anatoly is
working through his backlog. For example the mega256x patch was
committed to GCC recently (for 4.4). All I can ask of you is to have
patience. But please keep bugging us! :-) I definitely want to see that
these bugs get fixed.

Eric Weddington-----Original Message-----From: Andrew Hutchinson Sent: Sunday, March 16, 2008 10:06 AMTo: avr-gcc-l***@*ongnu.org; Weddington, Eric; Anatoly Sokolov
Subject: AVR bug fix status

Here is status of the bugs I have looked at.

Bug status needs updating to status in BugzillaFor example, confirm and update known to work/known to failinformation. I cannot do this.Some of the bugs are serious and generally I would adviseagainst using 4.3 - especially with long operands.Andy



--------------------------------------------------------------
-------------------------------------- gcc is pushing too many registershttp://gcc.gnu.org/bugzilla/show_bug.cgi?id=32871Patch created and submitted with Anatoly since 3/2/2008
--------------------------------------------------------------
--------------------------------------

Various BASE_POINTER spill failure ICE bugshttp://gcc.gnu.org/bugzilla/show_bug.cgi?id=19636http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31786http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24894http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31644Patch created and submitted with Anatoly since 1/16/2008
--------------------------------------------------------------
--------------------------------------
ICE in extract_insn, at recog.c:1990 AVR Tiny Stackhttp://gcc.gnu.org/bugzilla/show_bug.cgi?id=34412fixed and committed
--------------------------------------------------------------
--------------------------------------Incomplete check for pm() annotation/call through functionpointer goes to wrong addresshttp://gcc.gnu.org/bugzilla/show_bug.cgi?id=27192http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35013Patched posted 2/16/2008
--------------------------------------------------------------
--------------------------------------The following GCC bugs are not due to AVR backend - but causeproblems! COMBINE repeating same matches and canSEG fault]gcc.c-torture/execute/pr27364.c fails with -O1, -O2 and -Oshttp://gcc.gnu.org/bugzilla/show_bug.cgi?id=34916http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35519Combine bug posted with patch 3/9/2008
--------------------------------------------------------------
--------------------------------------
fwprop only propagates one operandmissed-optimization transforming a byte array to unsigned long(and perhaps many others)http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35542http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27663Bug reported 3/11/2008 with suggested patch

--------------------------------------------------------------
-------------------------------------- 4.3.0: size of small function increases from 2 to 29 wordshttp://gcc.gnu.org/bugzilla/show_bug.cgi?id=35507Outline solution posted 3/9/2008 - needs patch._______________________________________________
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.orghttp://lists.nongnu.org/mailman/listinfo/avr-gcc-list

Offline

#2 March 17, 2008 16:24:32

Andy H.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

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


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 targetI only have CYGWIN - which is way too slow for testsuite - I think ittakes 2/3 hours for just torture/execute and it would not be better forany other target.I looked at converting dejagnu - but first problem is that it uses aload of unix shell commands. They would need changing to DOS. So itsback in the "Too difficult" tray.Andy



_______________________________________________
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.orghttp://lists.nongnu.org/mailman/listinfo/avr-gcc-list

Offline

#3 March 19, 2008 20:16:44

Mike S.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

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


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.orghttp://lists.nongnu.org/mailman/listinfo/avr-gcc-list

Offline

Board footer

Moderator control

Enjoy the 11th of December
PoweredBy

The Forums are managed by develissimo stuff members, if you find any issues or misplaced content please help us to fix it. Thank you! Tell us via Contact Options
Leave a Message
Welcome to Develissimo Live Support