Has the changes that have gone into the check parallelization made the
.sum file non-deterministic?
I'm seeing a lot of small hunks in different orders which cause my
comparison scripts to show big differences.
I haven't been paying attention to the nature of the make check changes
so Im not sure if this is expected...
Or is this something else? Its the same code base between runs, just
with a few changes made to some include files.
ie: the order of the options -mstackrealign and -mno-stackrealign are
swapped in this output:
Running
/gcc/2014-09-16/gcc/gcc/testsuite/gcc.target/i386/stackalign/stackalign.exp
...
- UNSUPPORTED: gcc.target/i386/stackalign/asm-1.c -mstackrealign
UNSUPPORTED: gcc.target/i386/stackalign/asm-1.c -mno-stackrealign
! UNSUPPORTED: gcc.target/i386/stackalign/longlong-1.c -mstackrealign
UNSUPPORTED: gcc.target/i386/stackalign/longlong-1.c -mno-stackrealign
UNSUPPORTED: gcc.target/i386/stackalign/longlong-2.c -mstackrealign
UNSUPPORTED: gcc.target/i386/stackalign/longlong-2.c -mno-stackrealign
PASS: gcc.target/i386/stackalign/pr39146.c -mstackrealign (test for
excess errors)
--- 110393,110402 ----
PASS: gcc.target/i386/math-torture/trunc.c -O2 -flto
-fno-use-linker-plugin -flto-partition=none (test for excess errors)
PASS: gcc.target/i386/math-torture/trunc.c -O2 -flto
-fuse-linker-plugin -fno-fat-lto-objects (test for excess errors)
Running
/gcc/2014-09-16/gcc/gcc/testsuite/gcc.target/i386/stackalign/stackalign.exp
...
UNSUPPORTED: gcc.target/i386/stackalign/asm-1.c -mno-stackrealign
! UNSUPPORTED: gcc.target/i386/stackalign/asm-1.c -mstackrealign
UNSUPPORTED: gcc.target/i386/stackalign/longlong-1.c -mno-stackrealign
+ UNSUPPORTED: gcc.target/i386/stackalign/longlong-1.c -mstackrealign
UNSUPPORTED: gcc.target/i386/stackalign/longlong-2.c -mstackrealign
UNSUPPORTED: gcc.target/i386/stackalign/longlong-2.c -mno-stackrealign
PASS: gcc.target/i386/stackalign/pr39146.c -mstackrealign (test for
excess errors)
Andrew
