AW: AW: [avr-libc-dev] SIMULAVR / Test suite for binutils and gcc

[Björn Haase]

>>Therefore my question:
>>Does anyone has information on how gnu simulators are supposed to behave,
>>and/or are there activities under way to change something within the
>>simulavr interface (? simulavrxxxxx ?)?
>>
>>
>>
>
>I was just asking a similar question on the gcc list, see this thread here:
><http://gcc.gnu.org/ml/gcc/2004-12/msg00585.html>
>
>You'll probably have to ask the simulavr people for more information, or
>ask them to make the changes needed.

>Alternatively, there is Avrora:
><http://compilers.cs.ucla.edu/avrora/>
>Which has just been released and says it can be used as a GDB backend.
>
>I'm very intereted in how you got the testsuite working, even if
>partially. Do you have something written (a how-to) about it?
>
>Getting the GCC testuite running on the AVR is very badly needed work,
>and your efforts are very appreciated!
>
>Eric

Meanwhile I have advanced a little bit further. I now come to the
conclusion, that there is
no urgent need for a new interface of simulavr. We readily could use the
present one.
The price that one has to pay for the non-standard interface is, that the
templates
for the "target_board" expect scripts cannot be used. So far, I have a
script to replace
the original templates. This script, however, does not by far aim to be as
portable
and self-configuring as the original gnu templates. This, however, should
not be a
problem, as long as the environment is setup propperly (e.g. all executables
are
found within the search path, the avr linker nows where to find avr-libc
without explicit -L,
etc.  ).

What I am obtaining now is a *huge* number of failures. Many of them are of
the
type "your printf does not print doubles " or "your target malloc does not
behave as expected".
Next task would be to find a way to rule out all the tests that are not
relevant for
an embedded target. This will probably be *very* time consuming.

So far, I have been setting up the test suite using the atmega128 as
simulation target.
Since the tests are fairly time-consuming, I'd suggest that we first
concentrate on
one member per basic family "avr3,avr4, etc.". Among these families, it
would be best
to use targets that dispose of as much memory as possible.

Any suggestions, which targets to choose for the test suite? (Of course only
controllers can be used that are also supported by simulavr.)

Once I have translated the comments in my expect scripts to english, I will
post
them.

Yours,

Björn