> -----Original Message----- > From: Georg-Johann Lay [mailto:a...@gjlay.de] > Sent: Saturday, February 28, 2009 10:09 AM > To: Weddington, Eric > Cc: Nicholas Vinen; avr-gcc-list@nongnu.org > Subject: Re: [avr-gcc-list] Re: C vs. assembly performance > > Weddington, Eric schrieb: > > BTW, is there a reason why there is more than one bug list?
Yes, because there is more than one project. ;-) GNU Binutils GCC Avr-libc Each of those projects are separate and they each have their own bug list. WinAVR has its own bug list for 2 reasons: - There may be bugs to the installation itself, which has nothing to do with the underlying projects - It is used as a "catch-all" starting point for users who are not used to filing bug reports with open source projects. It is easier to point them there first, then then bugs can be analysed and reported to upstream projects. Although, I admit that I haven't gone through the WinAVR bug list with the intent to move bugs upstream in some time. I'm planning on doing that after the WinAVR release, to clean up a bit. I keep track of the AVR specific bugs in binutils, gcc, gdb here: <http://www.nongnu.org/avr-libc/bugs.html> And that page has links to the other projects' bug lists. Eric _______________________________________________ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
