Harel Cain
2009-Jul-14 10:35 UTC
[LLVMdev] Unexpected failures in the DejaGNU test collection
Hi all, When using "make check" with the DejaGNU test collection, I encounter two unexpected failures (they seem to be closely related). My question: are they well known, and if so what's the problem and how can I fix it? This is the error text I get: FAIL: /var/data/common/trunk/llvm/test/FrontendC/2008-05-19-AlwaysInline.c Failed with exit(1) at line 1 while running: /var/data/common/template_wc//install/bin/llvm-gcc -emit-llvm -w /var/data/common/trunk/llvm/test/FrontendC/2008-05-19-AlwaysInline.c -S -fno-unit-at-a-time -emit-llvm -O0 -o - | not /bin/grep sabrina /var/data/common/trunk/llvm/test/FrontendC/2008-05-19-AlwaysInline.c:12: error: inlined_to pointer is set but no predecessors found sabrina/2: (inline copy in bar/1) availability:available(0) needed tree finalized always_inline called by: calls: /var/data/common/trunk/llvm/test/FrontendC/2008-05-19-AlwaysInline.c:12: internal compiler error: verify_cgraph_node failed Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://developer.apple.com/bugreporter> for instructions. FAIL: /var/data/common/trunk/llvm/test/FrontendC/always-inline.c Failed with exit(1) at line 1 while running: /var/data/common/template_wc//install/bin/llvm-gcc -emit-llvm -w -S /var/data/common/trunk/llvm/test/FrontendC/always-inline.c -o - | /bin/grep call | not /bin/grep foo /var/data/common/trunk/llvm/test/FrontendC/always-inline.c:12: error: inlined_to pointer is set but no predecessors found foo/4: (inline copy in i_want_bar/3) availability:available(1) 16 insns needed tree finalized always_inline called by: calls: bar/0 /var/data/common/trunk/llvm/test/FrontendC/always-inline.c:12: internal compiler error: verify_cgraph_node failed Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://developer.apple.com/bugreporter> for instructions. Harel Cain
Jakob Stoklund Olesen
2009-Jul-14 11:01 UTC
[LLVMdev] Unexpected failures in the DejaGNU test collection
On 14/07/2009, at 12.35, Harel Cain wrote:> When using "make check" with the DejaGNU test collection, I encounter > two unexpected failures (they seem to be closely related). > My question: are they well known, and if so what's the problem and how > can I fix it?> FAIL: /var/data/common/trunk/llvm/test/FrontendC/2008-05-19- > AlwaysInline.c > FAIL: /var/data/common/trunk/llvm/test/FrontendC/always-inline.cHello Harel, Failures in the FrontendC test suite usually means that your llvm-gcc is older than your LLVM tree. Try compiling llvm-gcc from top-of-tree and see if the failures remain. Regards, /jakob
Daniel Dunbar
2009-Jul-14 15:49 UTC
[LLVMdev] Unexpected failures in the DejaGNU test collection
Since it came up, what is blocking us from putting these tests in the llvm-gcc test suite instead of in the LLVM test suite? - Daniel On Tue, Jul 14, 2009 at 4:01 AM, Jakob Stoklund Olesen<stoklund at 2pi.dk> wrote:> > On 14/07/2009, at 12.35, Harel Cain wrote: >> When using "make check" with the DejaGNU test collection, I encounter >> two unexpected failures (they seem to be closely related). >> My question: are they well known, and if so what's the problem and how >> can I fix it? > >> FAIL: /var/data/common/trunk/llvm/test/FrontendC/2008-05-19- >> AlwaysInline.c >> FAIL: /var/data/common/trunk/llvm/test/FrontendC/always-inline.c > > Hello Harel, > > Failures in the FrontendC test suite usually means that your llvm-gcc > is older than your LLVM tree. > > Try compiling llvm-gcc from top-of-tree and see if the failures remain. > > Regards, > /jakob > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Harel Cain
2009-Jul-15 12:44 UTC
[LLVMdev] Unexpected failures in the DejaGNU test collection
Hi Jakob, We're using unmodified release version 2.5 of both llvm and llvm-gcc-4.2 and that same problem I mentioned shows up in both the DejaGNU tests and in the test-suite, and I even checked on two different boxes. Everything else works perfectly. Nobody encountered those failures? Harel>> FAIL: /var/data/common/trunk/llvm/test/FrontendC/2008-05-19- >> AlwaysInline.c >> FAIL: /var/data/common/trunk/llvm/test/FrontendC/always-inline.c> Hello Harel, > > Failures in the FrontendC test suite usually means that your llvm-gcc > is older than your LLVM tree. > > Try compiling llvm-gcc from top-of-tree and see if the failures remain. > > Regards, > /jakob >
Possibly Parallel Threads
- [LLVMdev] Unexpected failures in the DejaGNU test collection
- [LLVMdev] Unexpected failures in the DejaGNU test collection
- [LLVMdev] dejagnu test failures on x86-32 linux
- [LLVMdev] DejaGNU test fixes
- [LLVMdev] XPASS forAsmBlocksComplexJumpTarget.c (-fasm-blocks)