GCC testsuite results needed

Actually we are planing to publish test results against QEMU M3 rather than M0/M4 as only M3 is officially supported by QEMU.

Hi Terry,
Thanks for the reply.
I have few more questions in addition.
1. Which version of gcc testsuite you validate the tools?
2. Do you use dejaGNU framework for validating gcc testsuite or any other tool?
3. Is it possible to provide test setup also?

Hi Vikram,

1. For our tool chain based on gcc 4.6, the test suites inside upstream gcc 4.6 are used. For our tool chain based on 4.7, the test suites inside upstream 4.7 are used.

2. Yes, we use dejaGNU. I think you mean performing gcc "make check" under gcc build folder aka gcc regression test. All tests are performed on QEMU M3.

3. Due to some legal concerns, I am sorry that the test setup can not be shared. But it isn't so complicated. You can try to start from the existing files. I am glad to provide help if you run into any problems during the setup.

Ok.. Thanks a lot.

Hi,

Are the test results shared now?
I have built toolchain and ran regression using qemu-system-arm. I want to check if the results are OK.

My test options and results summary:
Compiler options: (addition to options in arm-sim baseboard file)
-mthumb -mcpu=cortex-m3 --specs=rdimon.specs -lc -lrdimon

QEMU execute options:
-cpu cortex-m3 -nographic -serial null -monitor null -semihosting -kernel <executable file>

  === gcc Summary ===

# of expected passes 66124
# of unexpected failures 857
# of expected failures 183
# of unresolved testcases 1
# of unsupported tests 1247

  === g++ Summary ===

# of expected passes 43204
# of unexpected failures 102
# of unexpected successes 2
# of expected failures 279
# of unsupported tests 767