Displaying 2 results from an estimated 2 matches for "bitfield4".
Did you mean:
bitfield
2010 Jan 07
1
[LLVMdev] "Value has wrong type!" on Bool:4 bitfield
I've built a debug build of llvm 2.6, and llvm-gcc 2.6 for arm-elf
with --enable-checking=yes.
On the attached test case (which is g++.dg/expr/bitfield4.C from the
GCC 4.2 testsuite) I get:
$ cc1plus bitfield4.ii -emit-llvm-bc -o bitfield4.o -quiet
cc1plus: /home/foad/svn/antix/toolchain/branches/w/foad/2757llvm26/toolchain/llvm/llvm-gcc/gcc/llvm-convert.cpp:999:
llvm::Value* TreeToLLVM::Emit(tree_node*, const MemRef*): Assertion
`(Result == 0 ||...
2009 Jul 25
2
[LLVMdev] GCC DejaGNU regressions
...------ next part --------------
Note that this test rig does not record "failures." Instead, when a
test fails, it records that some previous revision of LLVM-GCC passed
that given test (i.e. it records regressions). Ergo, a line like this:
74228.prev/gcc.sum:PASS: gcc.dg/i386-bitfield4.c scan-assembler-not
movb
says "The r74228 checkout of LLVM-GCC passed the gcc.dg/i386-
bitfield4.c scan-assembler-not movb test, but the most recent LLVM-GCC
(r76963) failed."
stuart