search for: ubytety

...*DestP unsigned Align) { const Type *SBP = PointerType::get(Type::SByteTy); static Function *MemSet = 0; - if (!MemSet) - MemSet = TheModule->getOrInsertFunction("llvm.memset", Type::VoidTy, SBP, - Type::UByteTy, Type::UIntTy, + const Type *IntPtr = TD.getIntPtrType(); + if (!MemSet) { + const char *Name = IntPtr == Type::UIntTy ? + "llvm.memset.i32" : "llvm.memset.i64"; + MemSet = TheModule->getOrInsertFunction(Name, Type::VoidTy, SBP, +...

...stant. Any index into a structure must be a constant of type UByte, and so it should cast to a ConstantUInt. (Operand 0 is not a special case, but it is always an array index so it sometimes may not be a constant. Very often, though, it is the constant 0.) anyway, indexVal->getType() == Type::UByteTy should tell you if you have a structure index or not. --Vikram

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

Ok. Let's say I have a GetElementPtrInst that is used to access structure elements. In this case the indexes will be constants and I want to get the constant values as an a native C int. Now I can iterate over all the indexes with idx_begin(). I can cast all of the indexes to a ConstantIntegral. However, I cannot cast the indexes to a ConstantSInt or ConstantUInt (cast<> throws an

...onics. For example, DIV will be automatically converted to SDIV, UDIV or FDIV based on the operand types. Similarly for the other instructions to be changed. 6. The distinction between unsigned and signed types probably won't go away before release time. That is, we'll still have UByteTy and SByteTy, etc. The change to merge those to "Int8" will occur after the 1.9 release accompanied by another bytecode version change (version 7). Similarly for Short, Int and Long. 7. Until Release 1.9 goes out the door (Nov 6th), the definition of version 6 bytecode is in fl...

I have a question about GetElementPtr. Suppose I have an GetElementPtr Instruction GI: %reg = getelementptr %ST* %s, uint 1, ubyte 2, ubyte 1, uint 5, uint 13 I want to check if this is the reference of a component of a structure, how can I do that? Should I check which operand of this instruction is 'ubyte' type? How can I do that in code? should I use ubyte *a =

On Fri, 1 Sep 2006, Michael McCracken wrote: > Here's what works now, and I have a separate test case for each of these: > > statement functions > intrinsic functions (print, cos, etc) > loops, goto statments > scalarized array operations > function calls with *no arguments* > simple common blocks Great! > Function calls with more than one argument don't work.

The NIST F77 test suite doesn't seem to be compatible with gfortran at all, so I had to work from my own sample codes, and generate test cases from them. Here's what works now, and I have a separate test case for each of these: statement functions intrinsic functions (print, cos, etc) loops, goto statments scalarized array operations function calls with *no arguments* simple common