search for: getlementptr

...;getOperand(0)", but I can not get "%struct.Args* @globalArg", "i64 0", and "i32 2" in this instruction. I know I can get the indices of getelementptr instructions through "getOperand()", but now in the previous example, I want to get the indices from a getlementptr value. How should I do? Thank you in advance. Best Regards! -------------------------------------------- Qiuping Yi Institute Of Software Chinese Academy of Sciences -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attach...

When compiling to the x86-64 architecture, llc -fast generates incorrect assembly for the getlementptr instruction. This only seems to occur when llc is passed the fast flag. [tamirs at tuna compiler]$ cat jonx.ll ; ModuleID = '<stdin>' define i32 @main() { ret i32 0 } define i32 @_l5_get(i32 %t3, i32* %t1) { %t9 = getelementptr i32* %t1, i32 %t3 ; <i32*> [#uses=1] %...

...t I can not get "%struct.Args* @globalArg", "i64 0", and "i32 2" in this > instruction. > > I know I can get the indices of getelementptr instructions through > "getOperand()", but now in the previous example, > I want to get the indices from a getlementptr value. How should I do? > Thank you in advance. > > > Best Regards! > > -------------------------------------------- > Qiuping Yi > Institute Of Software > Chinese Academy of Sciences > _______________________________________________ > LLVM Developers mailing list...

...t;, "i64 0", and "i32 2" in > this > >> instruction. > >> > >> I know I can get the indices of getelementptr instructions through > >> "getOperand()", but now in the previous example, > >> I want to get the indices from a getlementptr value. How should I do? > >> Thank you in advance. > >> > >> > >> Best Regards! > >> > >> -------------------------------------------- > >> Qiuping Yi > >> Institute Of Software > >> Chinese Academy of Sciences > &g...

...`llvm.multidim.array.index.*` intrinsic is used to get the address of an element from an array. It performs address calcuation only and does not access memory. It is similar to `getelementptr`. However, it imposes additional semantics which allows the optimiser to provide better optimisations than `getlementptr`. ### Arguments: The first argument is always a type used as the basis for the calculations. The second argument is always a pointer, and is the base address to start the calculation from. The remaining arguments are a list of pairs. Each pair contains a dimension stride, and an offset with res...

...sic is used to get the address of >> an element from an array. It performs address calcuation only and >> does not access memory. It is similar to `getelementptr`. However, it imposes >> additional semantics which allows the optimiser to provide better optimisations >> than `getlementptr`. >> >> >> >> ### Arguments: >> >> The first argument is always a type used as the basis for the calculations. The >> second argument is always a pointer, and is the base address to start the >> calculation from. The remaining arguments are a list of...

...sic is used to get the address of > an element from an array. It performs address calcuation only and > does not access memory. It is similar to `getelementptr`. However, it imposes > additional semantics which allows the optimiser to provide better optimisations > than `getlementptr`. > > > > ### Arguments: > > The first argument is always a type used as the basis for the calculations. The > second argument is always a pointer, and is the base address to start the > calculation from. The remaining arguments are a list of pairs. Each pair...

...et the address of >>> an element from an array. It performs address calcuation only and >>> does not access memory. It is similar to `getelementptr`. However, it imposes >>> additional semantics which allows the optimiser to provide better optimisations >>> than `getlementptr`. >>> >>> >>> >>> ### Arguments: >>> >>> The first argument is always a type used as the basis for the calculations. The >>> second argument is always a pointer, and is the base address to start the >>> calculation from. The re...

...gt; > an element from an array. It performs address calcuation only and > > > does not access memory. It is similar to `getelementptr`. However, it imposes > > > additional semantics which allows the optimiser to provide better optimisations > > > than `getlementptr`. > > > > > > > > > > > > ### Arguments: > > > > > > The first argument is always a type used as the basis for the calculations. The > > > second argument is always a pointer, and is the base address to start the > > &...