Lines Matching full:myvar
110 %MyVar = uninitialized global i32
112 %idx1 = getelementptr i32, i32* %MyVar, i64 0
113 %idx2 = getelementptr i32, i32* %MyVar, i64 1
114 %idx3 = getelementptr i32, i32* %MyVar, i64 2
117 address of ``MyVar``. They compute, as follows (using C syntax):
121 idx1 = (char*) &MyVar + 0
122 idx2 = (char*) &MyVar + 4
123 idx3 = (char*) &MyVar + 8
127 accessed to make these computations because the address of ``%MyVar`` is passed
132 ``%MyVar`` global, which is only one ``i32`` long, not three ``i32``\s long.
183 %MyVar = uninitialized global { [40 x i32 ]* }
185 %idx = getelementptr { [40 x i32]* }, { [40 x i32]* }* %MyVar, i64 0, i32 0, i64 0, i64 17
187 In this example, we have a global variable, ``%MyVar`` that is a pointer to a
209 %MyVar = uninitialized global { [40 x i32 ] }
228 %MyVar = global { [10 x i32] }
229 %idx1 = getelementptr { [10 x i32] }, { [10 x i32] }* %MyVar, i64 0, i32 0, i64 1
230 %idx2 = getelementptr { [10 x i32] }, { [10 x i32] }* %MyVar, i64 1
233 array that is in the structure in ``%MyVar``, that is ``MyVar+4``. The type of
235 structure after ``%MyVar``. The type of ``idx2`` is ``{ [10 x i32] }*`` and its
236 value is equivalent to ``MyVar + 40`` because it indexes past the ten 4-byte
237 integers in ``MyVar``. Obviously, in such a situation, the pointers don't
251 %MyVar = global { [10 x i32] }
252 %idx1 = getelementptr { [10 x i32] }, { [10 x i32] }* %MyVar, i64 1, i32 0, i64 0
253 %idx2 = getelementptr { [10 x i32] }, { [10 x i32] }* %MyVar, i64 1
255 In this example, the value of ``%idx1`` is ``%MyVar+40`` and its type is
256 ``i32*``. The value of ``%idx2`` is also ``MyVar+40`` but its type is ``{ [10 x
