On 6/15/24 10:30, Georg-Johann Lay wrote:
Am 14.06.24 um 21:11 schrieb Detlef Vollmann:
I actually plan anyway to run a test with the built libstdc++ on
simulavr.
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).
Thanks for the pointer.
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.
avr-gcc 15 actually has 57 multilib variants (long-double32,
double64 and short-calls versions).
avr-libc 2.2.0 uses -print-multi-lib to build them all,
avr-libc 2.0.0 has only 17 variants hardcoded.
But right now I'm fighting against an ICE in cmath, i.e. so far
any tests of cmath fail...
I'll investigate this tomorrow and decide then what I'll do...
Detlef
