search for: mbuilder

...th chandra <sarathcse19 at gmail.com>wrote: > Hi James, > > First i converted the void * to int* and then did FPToSI...then did SHL...( > because CreateShl only accepts integers... i pointer casted it to int64 type > first)... Below is the code snippet.... > > > lhs = mBuilder.CreateStructGEP(firstArg, 0); > lhs = mBuilder.CreateLoad(lhs); > lhs = mBuilder.CreatePointerCast(lhs, PointerType::get( > mBuilder.getInt64Ty(), 0)); > int typelhs = getValueType(lhs); > rhs = mBuilder.CreateStructGEP(secondArg, 0); > rhs = mBuild...

...chandra <sarathcse19 at gmail.com<mailto:sarathcse19 at gmail.com>> wrote: Hi James, First i converted the void * to int* and then did FPToSI...then did SHL...( because CreateShl only accepts integers... i pointer casted it to int64 type first)... Below is the code snippet.... lhs = mBuilder.CreateStructGEP(firstArg, 0); lhs = mBuilder.CreateLoad(lhs); lhs = mBuilder.CreatePointerCast(lhs, PointerType::get( mBuilder.getInt64Ty(), 0)); int typelhs = getValueType(lhs); rhs = mBuilder.CreateStructGEP(secondArg, 0); rhs = mBuilder.CreateLoad(rhs); rhs =...

Hi, I'm pursuing M.Tech course. As a part of the project work i'm using LLVM as back-end. My project area is "Enhancing the performance of V8 javascript engine using LLVM as a back-end". Now i'm writing code for shift left(SHL) operator. I had my own Value Structure .. it's like this Struct Value { void *val ; char type; } The "char type" holds

...;sarathcse19 at gmail.com> > wrote:**** > > Hi James, > > First i converted the void * to int* and then did FPToSI...then did SHL...( > because CreateShl only accepts integers... i pointer casted it to int64 type > first)... Below is the code snippet.... > > > lhs = mBuilder.CreateStructGEP(firstArg, 0); > lhs = mBuilder.CreateLoad(lhs); > lhs = mBuilder.CreatePointerCast(lhs, PointerType::get( > mBuilder.getInt64Ty(), 0)); > int typelhs = getValueType(lhs); > rhs = mBuilder.CreateStructGEP(secondArg, 0); > rhs = mBuild...

...nd 64 bit), Linux, MacOS. We compile LLVM and our program with Microsoft's Visual Studio 2010. Both debug and release builds are affected. The variables are created en-block at the beginning of the function with code looking like for (i=0; i<513; ++i) { AllocaInst *variable = mBuilder.CreateAlloca(Type::getInt64Ty(mContext),0,""); mBuilder.CreateStore(GetConstI("INT4_8",0),variable); } We have not yet looked at the compiled machine code (same on Win 7 and 8, or differs?). But the 4k limit made us suspicious, as there were some bug reports - some still o...

...crosoft's Visual Studio 2010. Both debug and >> release builds are affected. >> >> The variables are created en-block at the beginning of the function >> with code looking like >> >> for (i=0; i<513; ++i) { >> AllocaInst *variable = >> mBuilder.CreateAlloca(Type::getInt64Ty(mContext),0,""); >> mBuilder.CreateStore(GetConstI("INT4_8",0),variable); >> } >> >> We have not yet looked at the compiled machine code (same on Win 7 and >> 8, or differs?). But the 4k limit made us suspicious, as t...

In Julia's use of LLVM, we were naming TBAA nodes with logic like this for LLVM 3.3: static MDNode *tbaa_make_child( const char *name, MDNode *parent, bool isConstant=false ) { MDNode *n = mbuilder->createTBAANode(name,parent,isConstant); n->setValueName( ValueName::Create(name, name+strlen(name))); return n; } The names would show up in dumps of the IR (e.g. "call F.dump()" from gdb) , which was really handy for debugging. But with LLVM 3.6's split of Value and...