search for: 2xi16

Displaying 3 results from an estimated 3 matches for "2xi16".

Did you mean: xi16
2011 Feb 24
0
[LLVMdev] Get Element Ptr inst
...x* %termptr.1, i32 0, > i32 5, i64 0, i64 0 ; <i16*> You should double-check the LangRef manual, but I think the problem stems from the fact that a GEP returns a pointer to the type found after all indexing is completed. So, in %tmp124, indexing %termptr.1 by i32 0 and i32 5 yields a [2xi16] type, and then the result of the GEP is a pointer to that, which is of type [2xi16] *. In the new GEP you've created, I think you can remove the first i64 0 index because the result of indexing i32 0 and i32 5 is a [2 x i16] and not a [2 x i16] *. -- John T. > > When I try to crea...
2011 Feb 24
1
[LLVMdev] Get Element Ptr inst
...i64 0, i64 0 ; <i16*> >> > > You should double-check the LangRef manual, but I think the problem stems > from the fact that a GEP returns a pointer to the type found after all > indexing is completed. > > So, in %tmp124, indexing %termptr.1 by i32 0 and i32 5 yields a [2xi16] > type, and then the result of the GEP is a pointer to that, which is of type > [2xi16] *. > > In the new GEP you've created, I think you can remove the first i64 0 index > because the result of indexing i32 0 and i32 5 is a [2 x i16] and not a [2 x > i16] *. > > -- Joh...
2011 Feb 24
2
[LLVMdev] Get Element Ptr inst
Given 2 GEPs as follows, %tmp124 = getelementptr inbounds %struct.termbox* %termptr.1, i32 0, i32 5, !dbg !1051 ; <[2 x i16]*> [#uses=1] %tmp125 = getelementptr inbounds [2 x i16]* %tmp124, i64 0, i64 0, !dbg !1051 ; <i16*> [#uses=1] can I replace the 2nd one with %tmp126 = getelementptr inbounds %struct.termbox* %termptr.1, i32 0, i32 5, i64 0, i64 0 ; <i16*> When I try to