Displaying 5 results from an estimated 5 matches for "j_addr".
Did you mean:
__addr
2010 May 13
4
[LLVMdev] How to get the variable mapping between the source and llvm bytecode
...'simplecase.c'
target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64"
target triple = "x86_64-unknown-linux-gnu"
define i32 @h(i32 %j, i32 %i) nounwind {
entry:
%j_addr = alloca i32 ; <i32*> [#uses=2]
%i_addr = alloca i32 ; <i32*> [#uses=2]
%retval = alloca i32 ; <i32*> [#uses=2]
%0 = alloca i32 ; <i32*> [#uses=2]
%tmp =...
2010 May 13
0
[LLVMdev] How to get the variable mapping between the source andllvm bytecode
...t; target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64"
> target triple = "x86_64-unknown-linux-gnu"
> define i32 @h(i32 %j, i32 %i) nounwind {
> entry:
> %j_addr = alloca i32 ; <i32*> [#uses=2]
> %i_addr = alloca i32 ; <i32*> [#uses=2]
> %retval = alloca i32 ; <i32*> [#uses=2]
> %0 = alloca i32 ; <i32*> [#us...
2010 May 14
2
[LLVMdev] How to get the variable mapping between the sourceandllvm bytecode
...yout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64"
>> target triple = "x86_64-unknown-linux-gnu"
>> define i32 @h(i32 %j, i32 %i) nounwind {
>> entry:
>> %j_addr = alloca i32 ; <i32*> [#uses=2]
>> %i_addr = alloca i32 ; <i32*> [#uses=2]
>> %retval = alloca i32 ; <i32*> [#uses=2]
>> %0 = alloca i32 ; <i...
2007 Apr 27
1
[LLVMdev] Preservance of function variables in the bytecode
Hello, LLVM-Dev guys.
I just wonder if function variables are preserved in the bytecode.
For example, are i and j in the following function preserved in .bc?
int sum(int i, int j){
int k;
k = i + j;
return k;
}
I tested this with "llc -march=c" and found this was converted to
int sum(int ltmp_0_1, int ltmp_1_1) {
return (ltmp_1_1 + ltmp_0_1);
}
Therefore, it seems
2007 Apr 27
0
[LLVMdev] Preservance of function variables in the bytecode
...es in the bytecode
>To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
>
>This is what the llvm assembly looks like when I compile your example:
>
>int %sum(int %i, int %j) {
>entry:
> %i_addr = alloca int ; <int*> [#uses=2]
> %j_addr = alloca int ; <int*> [#uses=2]
> %retval = alloca int, align 4 ; <int*> [#uses=2]
> %tmp = alloca int, align 4 ; <int*> [#uses=2]
> %k = alloca int, align 4 ; <int*> [#uses=2]
> &qu...