Displaying 5 results from an estimated 5 matches for "emitmemcpi".
Did you mean:
emitmemcpy
2007 Apr 20
2
[LLVMdev] llvm-gcc Bug, Looking for Advice on Fix
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,
2006 May 13
0
[LLVMdev] Re: New llvmgcc4 snapshot
Chris Lattner wrote:
>
> 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
2006 Mar 03
0
[LLVMdev] Re: Re: New GCC4-based C/C++/ObjC front-end for LLVM
On Thu, 2 Mar 2006, Chris Lattner wrote:
>> Any ideas what could be wrong?
>
> Sorry for the delay, please try this tarball:
> http://nondot.org/sabre/2006-03-02-llvm-gcc-4.tar.gz
Actually, do to a recent change in CVS, this tarball will probably not
work anymore. Please apply the attached (small) patch on top of it in
the gcc directory.
Worth noting, this front-end only works
2006 May 08
6
[LLVMdev] New llvmgcc4 snapshot
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
--
2006 Mar 02
4
[LLVMdev] Re: Re: New GCC4-based C/C++/ObjC front-end for LLVM
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