llvm dev - Dec 2010 - [LLVMdev] Bad gcc versions

Török Edwin <edwintorok at gmail.com> writes:
>> > Which regression tests are failing with LLVM 2.8 and GCC 4.4.x?
>> 
>> Too many to list.
>
> Can you give me 2 or 3 examples (that fail with LLVM 2.8 and GCC 4.4
> but work with LLVM 2.8 and GCC 4.3), also I'd like to know how they
> fail.
> If I have some time I'll check with my 4.4 to see if they fail.
Well, I have some failures even with 4.1.2, attached below.

I have hundreds of failures scattered all over the tests.

Often I run a few different builds in parallel, with different obj/build
directories.  Is it possible that the test infrastructure writes
something to the source directories or some common temp directory?  That
could confuse things when doing parallel build/test and would explain
all these failures.  When I don't run in parallel, things seem to work
much better.

                                   -Dave

[x86_64-off-dbg]: FAIL: Clang :: Driver/hello.c (1160 of 8402)
[x86_64-off-dbg]: ******************** TEST 'Clang :: Driver/hello.c'
FAILED ********************
[x86_64-off-dbg]: Script:
[x86_64-off-dbg]: --
[x86_64-off-dbg]:
/ptmp/dag/build.llvm.trunk.official.debug/x86_64-unknown-linux-gnu/Debug+Asserts/bin/clang
-ccc-echo -o
/ptmp/dag/build.llvm.trunk.official.debug/x86_64-unknown-linux-gnu/tools/clang/test/Driver/Output/hello.c.tmp
/ptmp/dag/llvm-project.official/llvm/trunk/tools/clang/test/Driver/hello.c 2>
/ptmp/dag/build.llvm.trunk.official.debug/x86_64-unknown-linux-gnu/tools/clang/test/Driver/Output/hello.c.tmp.log
[x86_64-off-dbg]: grep 'clang" -cc1 .*hello.c'
/ptmp/dag/build.llvm.trunk.official.debug/x86_64-unknown-linux-gnu/tools/clang/test/Driver/Output/hello.c.tmp.log
[x86_64-off-dbg]:
/ptmp/dag/build.llvm.trunk.official.debug/x86_64-unknown-linux-gnu/tools/clang/test/Driver/Output/hello.c.tmp
>
/ptmp/dag/build.llvm.trunk.official.debug/x86_64-unknown-linux-gnu/tools/clang/test/Driver/Output/hello.c.tmp.out
[x86_64-off-dbg]: grep "I'm a little driver, short and stout."
/ptmp/dag/build.llvm.trunk.official.debug/x86_64-unknown-linux-gnu/tools/clang/test/Driver/Output/hello.c.tmp.out
[x86_64-off-dbg]: --
[x86_64-off-dbg]: Exit Code: 1
[x86_64-off-dbg]: 
[x86_64-off-dbg]: ********************

[x86_64-off-dbg]: FAIL: LLVM ::
Analysis/BasicAA/2010-09-15-GEP-SignedArithmetic.ll (2727 of 8402)
[x86_64-off-dbg]: ******************** TEST 'LLVM ::
Analysis/BasicAA/2010-09-15-GEP-SignedArithmetic.ll' FAILED
********************
[x86_64-off-dbg]: Script:
[x86_64-off-dbg]: --
[x86_64-off-dbg]: opt <
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/BasicAA/2010-09-15-GEP-SignedArithmetic.ll
-basicaa -aa-eval -print-all-alias-modref-info -disable-output |& grep {1
may alias}
[x86_64-off-dbg]: --
[x86_64-off-dbg]: Exit Code: 1
[x86_64-off-dbg]: 
[x86_64-off-dbg]: ********************

[x86_64-off-dbg]: FAIL: LLVM :: Analysis/BasicAA/args-rets-allocas-loads.ll
(2728 of 8402)
[x86_64-off-dbg]: ******************** TEST 'LLVM ::
Analysis/BasicAA/args-rets-allocas-loads.ll' FAILED ********************
[x86_64-off-dbg]: Script:
[x86_64-off-dbg]: --
[x86_64-off-dbg]: opt -basicaa -aa-eval -print-all-alias-modref-info
-disable-output <
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/BasicAA/args-rets-allocas-loads.ll
|& FileCheck 
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/BasicAA/args-rets-allocas-loads.ll
[x86_64-off-dbg]: --
[x86_64-off-dbg]: Exit Code: 1
[x86_64-off-dbg]: Command Output (stderr):
[x86_64-off-dbg]: --
[x86_64-off-dbg]:
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/BasicAA/args-rets-allocas-loads.ll:171:10:
error: expected string not found in input
[x86_64-off-dbg]: ; CHECK: Both ModRef: Ptr: double* %arg_a0 <->
%normal_ret_a0 = call double* @normal_returner()
[x86_64-off-dbg]:          ^
[x86_64-off-dbg]: <stdin>:122:2: note: scanning from here
[x86_64-off-dbg]:  ModRef: Ptr: double* %arg_a0 <-> %normal_ret_a0 = call
double* @normal_returner() ; <double*> [#uses=1]
[x86_64-off-dbg]:  ^
[x86_64-off-dbg]: --
[x86_64-off-dbg]: 
[x86_64-off-dbg]: ********************

[x86_64-off-dbg]: FAIL: LLVM :: Analysis/BasicAA/featuretest.ll (2733 of 8402)
[x86_64-off-dbg]: ******************** TEST 'LLVM ::
Analysis/BasicAA/featuretest.ll' FAILED ********************
[x86_64-off-dbg]: Script:
[x86_64-off-dbg]: --
[x86_64-off-dbg]: opt <
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/BasicAA/featuretest.ll
-basicaa -gvn -instcombine -dce -S | FileCheck
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/BasicAA/featuretest.ll
[x86_64-off-dbg]: --
[x86_64-off-dbg]: Exit Code: 1
[x86_64-off-dbg]: Command Output (stderr):
[x86_64-off-dbg]: --
[x86_64-off-dbg]:
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/BasicAA/featuretest.ll:126:10:
error: expected string not found in input
[x86_64-off-dbg]: ; CHECK: ret i16 %.ret
[x86_64-off-dbg]:          ^
[x86_64-off-dbg]: <stdin>:58:32: note: scanning from here
[x86_64-off-dbg]: define i16 @zext_sext_confusion(i16* %row2col, i5 %j) nounwind
{
[x86_64-off-dbg]:                                ^
[x86_64-off-dbg]: <stdin>:60:2: note: possible intended match here
[x86_64-off-dbg]:  ret i16 0
[x86_64-off-dbg]:  ^
[x86_64-off-dbg]: --
[x86_64-off-dbg]: 
[x86_64-off-dbg]: ********************

[x86_64-off-dbg]: FAIL: LLVM :: Analysis/BasicAA/getmodrefinfo-cs-cs.ll (2736 of
8402)
[x86_64-off-dbg]: ******************** TEST 'LLVM ::
Analysis/BasicAA/getmodrefinfo-cs-cs.ll' FAILED ********************
[x86_64-off-dbg]: Script:
[x86_64-off-dbg]: --
[x86_64-off-dbg]: opt <
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/BasicAA/getmodrefinfo-cs-cs.ll
-basicaa -aa-eval -print-all-alias-modref-info -disable-output |& FileCheck
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/BasicAA/getmodrefinfo-cs-cs.ll
[x86_64-off-dbg]: --
[x86_64-off-dbg]: Exit Code: 1
[x86_64-off-dbg]: Command Output (stderr):
[x86_64-off-dbg]: --
[x86_64-off-dbg]:
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/BasicAA/getmodrefinfo-cs-cs.ll:4:10:
error: expected string not found in input
[x86_64-off-dbg]: ; CHECK: Just Ref: call void @ro() <-> call void @f0()
[x86_64-off-dbg]:          ^
[x86_64-off-dbg]: <stdin>:1:1: note: scanning from here
[x86_64-off-dbg]: Function: test0: 0 pointers, 2 call sites
[x86_64-off-dbg]: ^
[x86_64-off-dbg]: <stdin>:5:2: note: possible intended match here
[x86_64-off-dbg]:  NoModRef: Ptr: i8* @B <-> call void
@llvm.memset.p0i8.i64(i8* @A, i8 0, i64 1, i32 1, i1 false)
[x86_64-off-dbg]:  ^
[x86_64-off-dbg]: --
[x86_64-off-dbg]: 
[x86_64-off-dbg]: ********************

[x86_64-off-dbg]: FAIL: LLVM :: Analysis/RegionInfo/mix_1.ll (2791 of 8402)
[x86_64-off-dbg]: ******************** TEST 'LLVM ::
Analysis/RegionInfo/mix_1.ll' FAILED ********************
[x86_64-off-dbg]: Script:
[x86_64-off-dbg]: --
[x86_64-off-dbg]: opt -regions -analyze <
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/RegionInfo/mix_1.ll |
FileCheck
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/RegionInfo/mix_1.ll
[x86_64-off-dbg]: opt -regions -stats <
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/RegionInfo/mix_1.ll
|& FileCheck -check-prefix=STAT
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/RegionInfo/mix_1.ll
[x86_64-off-dbg]: opt -regions -print-region-style=bb  -analyze <
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/RegionInfo/mix_1.ll
|& FileCheck -check-prefix=BBIT
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/RegionInfo/mix_1.ll
[x86_64-off-dbg]: opt -regions -print-region-style=rn  -analyze <
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/RegionInfo/mix_1.ll
|& FileCheck -check-prefix=RNIT
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/RegionInfo/mix_1.ll
[x86_64-off-dbg]: --
[x86_64-off-dbg]: Exit Code: 1
[x86_64-off-dbg]: Command Output (stderr):
[x86_64-off-dbg]: --
[x86_64-off-dbg]: opt: Unknown command line argument '-regions'.  Try:
'opt -help'
[x86_64-off-dbg]:
/ptmp/dag/llvm-project.official/llvm/trunk/test/Analysis/RegionInfo/mix_1.ll:51:10:
error: expected string not found in input
[x86_64-off-dbg]: ; CHECK: [0] 0 => <Function Return>
[x86_64-off-dbg]:          ^
[x86_64-off-dbg]: <stdin>:1:1: note: scanning from here
[x86_64-off-dbg]: 
[x86_64-off-dbg]: ^
[x86_64-off-dbg]: --
[x86_64-off-dbg]: 
[x86_64-off-dbg]: ********************

[x86_64-off-dbg]: FAIL: LLVM :: Bitcode/null-type.ll (3030 of 8402)
[x86_64-off-dbg]: ******************** TEST 'LLVM ::
Bitcode/null-type.ll' FAILED ********************
[x86_64-off-dbg]: Script:
[x86_64-off-dbg]: --
[x86_64-off-dbg]: not llvm-dis <
/ptmp/dag/llvm-project.official/llvm/trunk/test/Bitcode/null-type.ll.bc >
/dev/null |& grep "Invalid MODULE_CODE_FUNCTION record"
[x86_64-off-dbg]: --
[x86_64-off-dbg]: Exit Code: 1
[x86_64-off-dbg]: 
[x86_64-off-dbg]: ********************

greened at obbligato.org (David A. Greene) writes:
> Often I run a few different builds in parallel, with different obj/build
> directories.  Is it possible that the test infrastructure writes
> something to the source directories or some common temp directory?  That
> could confuse things when doing parallel build/test and would explain
> all these failures.  When I don't run in parallel, things seem to work
> much better.
There is definitely something to this.  If I take a random failing
testcase and run the test in isolation in the shell, it works.  So what,
if anything, does lit/FileCheck/etc. do that might run interference
if there is another copy of lit/FileCheck/etc. running at the same time?
I tried strace -etrace=file but nothing obvious pops out.

                               -Dave

On Thu, 09 Dec 2010 11:24:19 -0600
greened at obbligato.org (David A. Greene) wrote:
> greened at obbligato.org (David A. Greene) writes:
> 
> > Often I run a few different builds in parallel, with different
> > obj/build directories.  Is it possible that the test infrastructure
> > writes something to the source directories or some common temp
> > directory?  That could confuse things when doing parallel
> > build/test and would explain all these failures.  When I don't run
> > in parallel, things seem to work much better.
> 
> There is definitely something to this.  If I take a random failing
> testcase and run the test in isolation in the shell, it works.  So
> what, if anything, does lit/FileCheck/etc. do that might run
> interference if there is another copy of lit/FileCheck/etc. running
> at the same time? I tried strace -etrace=file but nothing obvious
> pops out.
I don't see anything wrong with FileCheck either.

However looks here, that .bc file is in the *source* tree, not the obj tree:
not llvm-dis <
/ptmp/dag/llvm-project.official/llvm/trunk/test/Bitcode/null-type.ll.bc >
/dev/null |& grep "Invalid MODULE_CODE_FUNCTION record"

And I guess the .bc file is created by something during the test, multiple
builds in parallel == everything breaks.
Daniel, is the .bc file created by 'lit'?

Best regards,
--Edwin