Displaying 7 results from an estimated 7 matches for "loadinstr".
Did you mean:
loadinst
2013 Jan 24
2
[LLVMdev] llvm alloca dependencies
...oad, recursively, to the beginning.
If you hit an alloca, stop.
> I tried to use methods from DependencyAnalysis class.
DependenceAnalysis. Seems like a bad start.
Dependence analysis is used to determine how two
array references may interact. Nothing to do with alloca.
> 1. if (DA.depends(loadInstrArray[i],loadInstrArray[j],false)) - no result
I can't say if this is correct or not without a more complete example.
For instance, in the code
for (i = 0; i < n; i += 2) {
loadInstr[i] = 0;
j = i + 1;
loadInstr[j] = 1;
}
there is no dependence between the t...
2013 Jan 25
2
[LLVMdev] llvm alloca dependencies
...top.
>
> > I tried to use methods from DependencyAnalysis class.
>
> DependenceAnalysis. Seems like a bad start.
> Dependence analysis is used to determine how two
> array references may interact. Nothing to do with alloca.
>
> > 1. if (DA.depends(loadInstrArray[i],loadInstrArray[j],false)) - no result
>
> I can't say if this is correct or not without a more complete example.
> For instance, in the code
>
> for (i = 0; i < n; i += 2) {
> loadInstr[i] = 0;
> j = i + 1;
>...
2013 Jan 25
0
[LLVMdev] llvm alloca dependencies
...f you hit an alloca, stop.
>
> > I tried to use methods from DependencyAnalysis class.
>
> DependenceAnalysis. Seems like a bad start.
> Dependence analysis is used to determine how two
> array references may interact. Nothing to do with alloca.
>
> > 1. if (DA.depends(loadInstrArray[i],loadInstrArray[j],false)) - no result
>
> I can't say if this is correct or not without a more complete example.
> For instance, in the code
>
> for (i = 0; i < n; i += 2) {
> loadInstr[i] = 0;
> j = i + 1;
> loadInstr[j] = 1;
>...
2013 Jan 25
0
[LLVMdev] llvm alloca dependencies
...I tried to use methods from DependencyAnalysis class.
>>
>> DependenceAnalysis. Seems like a bad start.
>> Dependence analysis is used to determine how two
>> array references may interact. Nothing to do with alloca.
>>
>> > 1. if (DA.depends(loadInstrArray[i],**loadInstrArray[j],false)) -
>> no result
>>
>> I can't say if this is correct or not without a more complete example.
>> For instance, in the code
>>
>> for (i = 0; i < n; i += 2) {
>> loadInstr[i] = 0;
>>...
2011 Mar 26
2
[LLVMdev] How to read memory data througn adress of unsigned long
I have a value of long type and like to get the data at the adress in the value:
#################
unsigned long v = 0xc0008000
Value* addr = ConstantInt::get(getIntegerType(64), v)
####################
Then I try to use LoadInstr to get a load instruction of ir as the following:
############################
Value* data = new LoadInst(addr, "", false, bb);
encounter segmentation fault.
########################
I also try to use IntToPtrInstr to do some transform as the following:
################################...
2015 May 28
1
[LLVMdev] Passing ConstantDataArray to GetElementPtrInst
...er.CreateGEP(strValue, index_vector, "tmp1");
args.push_back(valueAsPtr);
Builder.CreateCall(TheModule->getFunction("printf"), args, "callprintf");
Note that this is summarized, I already have the IRBuilder, etc initialized.
I've also tried this with a LoadInstr that loads the ConstantDataArray (I
just inserted strValue into the example code to simplify things, I get the
same error either way).
If I run this code, LLVM asserts in the CreateGEP call with the error
message "Non-pointer type for constant GetElementPtr expression" since the
type I...
2011 Mar 26
0
[LLVMdev] How to read memory data througn adress of unsigned long
...;blackfin.kang at gmail.com> wrote:
> I have a value of long type and like to get the data at the adress in the value:
>
> #################
> unsigned long v = 0xc0008000
> Value* addr = ConstantInt::get(getIntegerType(64), v)
> ####################
>
> Then I try to use LoadInstr to get a load instruction of ir as the following:
> ############################
> Value* data = new LoadInst(addr, "", false, bb);
> encounter segmentation fault.
> ########################
>
Perhaps you should use a debug build of LLVM so you get an assert
message inste...