AVR testing [was Re: Revised release criteria for GCC 4.0]

[E. Weddington]

Bernardo Innocenti wrote:

> Hans-Peter Nilsson wrote:
>
>> The presence of a turn-key simulator as per simtest-howto.html
>> makes it *immensely* more simple for others than hardware
>> holders to regression-test their GCC changes, verify bugs and
>> fix them.  So all the shouting from AVR enthusiasts is suggested
>> be better spent getting an AVR simulator and a newlib port in
>> the tree.
>
>
> I forgot to say that the AVR simulator is a GPL'd project
> on Savannah:
>
>  http://savannah.nongnu.org/projects/simulavr
>
> There's also a gdb-remote debugger for JTAG ICEs:
>
>  http://sourceforge.net/projects/avarice/
>
>
> AFAIK, these projects have never tried merging into
> gdb... and perhaps they should consider it.
>
[Getting OT]

Bernardo,

Both of these projects are going through upheavals at the moment for 
different reasons. SimulAVR is going through changes to its internal 
architecture, and new management has taken over. Both Avarice and 
SimulAVR (and many other AVR projects) have just lost a long time 
volunteer developer due to health issues, and this developer just 
happens to be the AVR port maintainer for GDB. Avarice could be in need 
of new maintainer. So a lot of things are in flux right now and there 
seems to be some interest into finally getting a system together that 
can do more simulation as well as be used for running the testsuite. But 
this is getting OT for the gcc list, better to take this to the 
avr-gcc-list <http://www.avr1.org/mailman/listinfo/avr-gcc-list>.