search for: emitmemcpy

Ok, I've tracked down the problem I've had bootstrapping llvm-gcc. The culprit is in TreeToLLVM::EmitMemCpy: void TreeToLLVM::EmitMemCpy(Value *DestPtr, Value *SrcPtr, Value *Size, unsigned Align) { const Type *SBP = PointerType::get(Type::Int8Ty); const Type *IntPtr = TD.getIntPtrType(); Value *Ops[4] = { CastToType(Instruction::BitCast, DestPtr, SBP), Ca...

...c-4/gcc/llvm-backend.cpp:387: error: (Each undeclared identifier is reported only once for each function it appears in.) Adding: #include "llvm/Target/TargetData.h" Fixed this. Then I get: ../../2006-05-08-llvm-gcc-4/gcc/llvm-convert.cpp: In member function `void TreeToLLVM::EmitMemCpy(llvm::Value*, llvm::Value*, llvm::Value*, unsigned int)': ../../2006-05-08-llvm-gcc-4/gcc/llvm-convert.cpp:800: error: `getIntPtrType' undeclared (first use this function) Which is fixed in exactly same way. And then the same change in needed in llvm-types.cpp. Chris, any change you...

...-Chris -- http://nondot.org/sabre/ http://llvm.org/ -------------- next part -------------- Index: llvm-convert.cpp =================================================================== --- llvm-convert.cpp (revision 111673) +++ llvm-convert.cpp (working copy) @@ -795,14 +795,18 @@ void TreeToLLVM::EmitMemCpy(Value *DestP unsigned Align) { const Type *SBP = PointerType::get(Type::SByteTy); static Function *MemCpy = 0; - if (!MemCpy) - MemCpy = TheModule->getOrInsertFunction("llvm.memcpy", Type::VoidTy, SBP, -...

Hi All, There's a new snapshot of llvmgcc4 available here: http://nondot.org/sabre/2006-05-08-llvm-gcc-4.tar.gz This release includes the various portability fixes contributed on llvmdev, includes fixes to build with mainline CVS (and, thus, *requires* mainline CVS), and includes various other bug fixes. If you're interested, please try it out. Thanks, -Chris --

On Thu, 2 Mar 2006, Vladimir Prus wrote: >>> The instructions seem to have one path wrong. It says to get: >> >> I'll put together a tarball today. That will be easier than dealing with >> a patch, and it will include a bunch of bugfixes since the previous email. > Further into process, I get this error: > In file included from