Displaying 5 results from an estimated 5 matches for "llvmbuildgep".
2011 Jul 09
1
[LLVMdev] getting and setting array indices c interface
...re out how to get and set array indices from the c
interface.
so to get an element I'm calling
tindex = *fn\SymbolTable(*index\name)
index = LLVMBuildLoad(builder,tindex,"index")
arr = *fn\SymbolTable(*array\name)
arrptr = LLVMBuildLoad(Builder,arr,"arrayptr")
tmp = LLVMBuildGEP(Builder,arrptr,index,0,"ptr")
ptr = llvmBuildload(Builder,tmp,"ele")
and to set
tarr = *fn\SymbolTable(*array\name)
Arr = LLVMBuildLoad(builder,tarr,"array")
tval = *fn\SymbolTable(*value\name)
val = LLVMBuildLoad(builder,tval,"val")
tindex = *fn\S...
2015 Aug 17
2
[LLVMdev] [RFC] Developer Policy for LLVM C API
...u have more person in that thread saying they'd
need it and have to do various workaround to get things done without it.
>
>> - Let's say you remove types from pointers.
>>
>> This is a change that can be seen coming up. So, one should fairly early
>> on add an LLVMBuildGEP2 function that takes the extra type argument. Leave
>> the old function name around for now (deprecated), because with the current
>> state of LLVM, it can continue to work just fine.
>>
>> When LLVM is changed to *actually* remove all pointer types in its core,
>> the...
2015 Aug 17
6
[LLVMdev] [RFC] Developer Policy for LLVM C API
...keep working. There's no real need to
remove the old deprecated functions -- they'll keep working as well as they
ever did with the smaller-valued attributes.
- Let's say you remove types from pointers.
This is a change that can be seen coming up. So, one should fairly early on
add an LLVMBuildGEP2 function that takes the extra type argument. Leave the
old function name around for now (deprecated), because with the current
state of LLVM, it can continue to work just fine.
When LLVM is changed to *actually* remove all pointer types in its core,
then the LLVMBuildGEP function cannot reasonabl...
2013 Sep 30
1
[LLVMdev] RFC: llvm-shlib-test (Was: [llvm] r191029 - llvm-c: Make LLVMGetFirstTarget a proper prototype)
Attached is what I got thus far.
What I'm struggling with is proper integration in build system. What
is in there is just wild guesses from my side, both on autoconf and
cmake variants. It would be great if someone with proper knowledge of
the buildsystems could have a look. Also I'm not sure how to properly
handle compilation on msvc - clearly "-std=c11 -Wstrict-prototypes" is
2015 Aug 17
3
[LLVMdev] [RFC] Developer Policy for LLVM C API
On Sun, Aug 16, 2015 at 10:34 PM, deadal nix via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
> 2015-08-16 21:51 GMT-07:00 Eric Christopher <echristo at gmail.com>:
>>
>> The promise of stability. We don't promise that the C++ API will stay
>> stable.
>>
>
>
> Why was that promise be made in the first place ? Has it been made in the
>