GCC testsuite results

Asked by Senthil Kumar Selvaraj

Can you share results for the gcc testsuite for M3 tested on qemu? We'd like to make sure our build process/infrastructure did not introduce any regressions.

Question information

Language:
English Edit question
Status:
Answered
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Senthil Kumar Selvaraj (senthil-thecoder) said :
#1

This is what we get

   === gcc tests ===

 Schedule of variations:
     arm-qemu/-mthumb/-mcpu=cortex-m3

   === gcc Summary ===

 # of expected passes 86989
 # of unexpected failures 25
 # of expected failures 108
 # of unresolved testcases 1
 # of unsupported tests 4092

   === g++ Summary ===

 # of expected passes 76703
 # of unexpected failures 6
 # of expected failures 260
 # of unresolved testcases 2
 # of unsupported tests 3937

Revision history for this message
Thomas Preud'homme (thomas-preudhomme) said :
#2

Hi Senthil Kumar,

For our 2016Q1 release we had:

                === gcc Summary ===

# of expected passes 86991
# of unexpected failures 23
# of expected failures 108
# of unsupported tests 4092

# of expected passes 76704
# of unexpected failures 5
# of expected failures 260
# of unresolved testcases 1
# of unsupported tests 3937

If you send us the .sum files we can tell you which one are different compared to us.

Best regards.

Revision history for this message
Senthil Kumar Selvaraj (senthil-thecoder) said :
#3

I've uploaded the gcc and g++ sum files to http://distribute.atmel.no/tools/opensource/.temp

Would be great if you could tell us which test results differ.

Revision history for this message
Thomas Preud'homme (thomas-preudhomme) said :
#4

Hi,

Comparing the two the difference seems to be in gcc.dg/cdce1.c (internal compiler error) and g++.dg/lto/20081219 (also internal compiler error). We also noticed that last one on our own but it does not happen on our automated testing. It seems to depend on the environment so I'd focus on the first test failure.

=== compare_tests output for gcc.sum ===

Tests that now fail, but worked before:

arm-qemu/-mthumb/-mcpu=cortex-m3: gcc.dg/cdce1.c (test for excess errors)

New tests that FAIL:

arm-qemu/-mthumb/-mcpu=cortex-m3: gcc.dg/cdce1.c (internal compiler error)

Old tests that passed, that have disappeared: (Eeek!)

arm-qemu/-mthumb/-mcpu=cortex-m3: gcc.dg/cdce1.c execution test

=== compare_tests output for g++.sum ===

New tests that FAIL:

arm-qemu/-mthumb/-mcpu=cortex-m3: g++.dg/lto/20081219 cp_lto_20081219_0.o-cp_lto_20081219_1.o link, -fPIC -flto -flto-partition=1to1 -O2 (internal compiler error)

Old tests that passed, that have disappeared: (Eeek!)

arm-qemu/-mthumb/-mcpu=cortex-m3: g++.dg/lto/20081219 cp_lto_20081219_0.o-cp_lto_20081219_1.o link, -fPIC -flto -flto-partition=1to1 -O2

Can you help with this problem?

Provide an answer of your own, or ask Senthil Kumar Selvaraj for more information if necessary.

To post a message you must log in.