llvm dev - Aug 2009 - [LLVMdev] Is the head of llvm-gcc not working with the head of llvm for anyone else?

I just tried to compile llvm-gcc against the top of llvm and I ran
into this error:

/.../llvm/llvm-gcc-build/./prev-gcc/xgcc
-B/.../llvm/llvm-gcc-build/./prev-gcc/
-B/.../llvm/llvm-gcc-install/x86_64-unknown-linux-gnu/bin/ -c
-DHAVE_CONFIG_H -g -O2 -I.
-I/.../llvm/llvm-gcc-4.2/libiberty/../include  -W -Wall -pedantic
-Wwrite-strings -Wstrict-prototypes -Wc++-compat
/.../llvm/llvm-gcc-4.2/libiberty/fibheap.c -o fibheap.o
cc1: .../llvm/llvm/include/llvm/CodeGen/ValueTypes.h:229: unsigned int
llvm::MVT::getSizeInBits() const: Assertion `0 && "getSizeInBits
called on extended MVT."' failed.

Is anyone else getting this, or did I configure llvm-gcc to build
incorrectly? This is what I specified:
> mkdir build
> cd build
> $LLVMGCC/configure --prefix=`pwd`/../install --program-prefix=llvm-
--enable-llvm=$LLVMOBJDIR/build --enable-languages=c,c++

On Aug 15, 2009, at 5:05 PM, Erick Tryzelaar wrote:
> I just tried to compile llvm-gcc against the top of llvm and I ran
> into this error:
>
> /.../llvm/llvm-gcc-build/./prev-gcc/xgcc
> -B/.../llvm/llvm-gcc-build/./prev-gcc/
> -B/.../llvm/llvm-gcc-install/x86_64-unknown-linux-gnu/bin/ -c
> -DHAVE_CONFIG_H -g -O2 -I.
> -I/.../llvm/llvm-gcc-4.2/libiberty/../include  -W -Wall -pedantic
> -Wwrite-strings -Wstrict-prototypes -Wc++-compat
> /.../llvm/llvm-gcc-4.2/libiberty/fibheap.c -o fibheap.o
> cc1: .../llvm/llvm/include/llvm/CodeGen/ValueTypes.h:229: unsigned int
> llvm::MVT::getSizeInBits() const: Assertion `0 &&
"getSizeInBits
> called on extended MVT."' failed.
>
> Is anyone else getting this, or did I configure llvm-gcc to build
> incorrectly? This is what I specified:
>
Are you sure your llvm-gcc is up-to-date? Did you try a fresh build? :-)

-bw

On Sat, Aug 15, 2009 at 5:19 PM, Bill Wendling<isanbard at gmail.com>
wrote:
> On Aug 15, 2009, at 5:05 PM, Erick Tryzelaar wrote:
>
> Are you sure your llvm-gcc is up-to-date? Did you try a fresh build? :-)
>
> -bw
>
>
Yep, it was with a completely fresh checkout, and for the sake of
completeness, I did both a fresh rebuild of llvm and llvm-gcc.