Am 14.06.24 um 21:11 schrieb Detlef Vollmann:
I actually plan anyway to run a test with the built libstdc++ on simulavr.
Detlef
As an aside, simulavr tries to simulate an exact match of the hardware
including internal I/O like timers, IRQs, etc.
For GCC regression testing, no internal I/O is needed; all what's
required for testing algorithms is a core simulator like avrtest:
https://github.com/sprintersb/atest
https://github.com/sprintersb/atest?tab=readme-ov-file#running-the-avr-gcc-testsuite-using-the-avrtest-simulator
avrtest runs orders of magnitude faster than simulavr, however it
doesn't implement a GDB server, EEPROM or timers (none of which
is required for the GCC testsuite).
Apart from that, only being a core simulator, you can test for more
cores than covered by simulavr. simulavr supports devices that cover
the following 8 multilib variants:
avr2
tiny-stack
avr25
avr25/tiny-stack
avr4
avr5
avr51
avr6
out of the 19 variants available in avr-gcc, like avr3, avr31,
avrtiny, and all the avrxmega[2-7] variants that can be used with
avrtest.
avrtest comes with board descriptions that cover a variety
of all the different cores.
avrtest board descriptions usually supply more RAM than the
actual device has, which allows more PASSes due to less
out-of-memory FAILs.
Johann
