Re: [avr-gcc-list] AVR GDB testsuite

[Paulo Marques]

Weddington, Eric wrote:
> Paulo Marques wrote:
>> Joerg Wunsch wrote:
>>> As Weddington, Eric wrote:
>>>
>>>> Except that you might recall that avrtest was adapted from the
>>>> original core of simulavr. That's what made me wonder if it might
>>>> work...
>>> I didn't know that.  However, I'd be surprised if the rather esoteric
>>> feature of terminating with a "coredump" has been retained, too.  The
>>> avr-libc testsuite heavily relies on that feature, in order to analyze
>>> the simulator state "post mortem".
>> Just to clarify, you're both correct :)
> 
> LOL!
> 
> Then help us out Paolo, do you think that avrtest could be used in
> the current avr-libc testsuite? Or will modifications need to be done?

I don't know very well the details of the avr-libc testsuite, but from
what I could understand I can see several things that would need to be
done in order to use avrtest:

 - option to do a "gdb compatible" elf core dump file with the memory
contents at the time of exit / abort

 - add more support for different instruction families with errors on
opcodes not supported by the requested family

 - add support for devices with different RAM / flash sizes / maps

As Joerg said this would require manpower... :(

Humm... I looked at the test script and it seems it only uses the core
dump file to "artistically" extract the contents of r24:r25. This should
be much easier to implement than a full fledged core dump (but I could
have missed something).

As for the other 2 items, they should be easier if the testsuite is not
ran against a lot of MCU's, but just a few select ones.

Anyway, as you can see by the time it took me to reply to this post, I
really don't have time right now to help on this. So this is more a
question of: is there anyone out there that has the time and thinks this
project is worth his time?

-- 
Paulo Marques
Software Development Department - Grupo PIE, S.A.
Phone: +351 252 290600, Fax: +351 252 290601
Web: www.grupopie.com

"This version has many new and good features. Sadly, the good ones are
not new and the new ones are not good."