Displaying 5 results from an estimated 5 matches for "jitengine".
2013 Mar 30
2
[LLVMdev] Missed optimisation opportunities?
...ret=0, ll_last=0, ll_last2=1
if isnull(al_x) then
return al_x
end if
ll_i=1
do while ll_i<=al_x
ll_ret=ll_last+ll_last2
ll_last2=ll_last
ll_last=ll_ret
ll_i++
loop
return ll_ret
end function
With the following function passes;
FunctionPasses->add(new DataLayout(*JITEngine->getDataLayout()));
FunctionPasses->add(createBasicAliasAnalysisPass());
FunctionPasses->add(createPromoteMemoryToRegisterPass());
FunctionPasses->add(createInstructionCombiningPass());
FunctionPasses->add(createReassociatePass());
FunctionPass...
2013 Nov 23
2
[LLVMdev] GVN fails with bitcasts
Hi,
i have the following code:
define internal %"struct.dexter::ConditionConstant"*
@_ZN6dexter18BinaryConditionAdd8evaluateEv5(%"class.dexter::BinaryConditionAdd"*)
{
entry:
%1 = getelementptr inbounds %"class.dexter::BinaryConditionAdd"* %0, i32
0, i32 0, i32 1
%2 = load %"class.dexter::BaseCondition"** %1, align 8
%3 = bitcast
2009 Mar 11
0
[LLVMdev] Creating Pointer Constants
On 2009-03-08, at 12:46, Nyx wrote:
> I am writing a JIT compiler for a subset of the Matlab language and
> as a
> part of my implementation, I would like to be able to pass a constant
> pointer to a native function I'm calling.
>
> Right now, this is what I do:
>
> llvm::Constant* constInt = llvm::ConstantInt::get(llvm::Type::Int64Ty,
> (int64)thePointer);
>
2009 Mar 08
2
[LLVMdev] Creating Pointer Constants
Hello,
I am writing a JIT compiler for a subset of the Matlab language and as a
part of my implementation, I would like to be able to pass a constant
pointer to a native function I'm calling.
Right now, this is what I do:
llvm::Constant* constInt = llvm::ConstantInt::get(llvm::Type::Int64Ty,
(int64)thePointer);
llvm::Value* constPtr = llvm::ConstantExpr::getIntToPtr(constInt,
2018 Sep 15
4
LLVMContext: Threads and Ownership.
Hi All,
ORC's new concurrent compilation model generates some interesting lifetime
and thread safety questions around LLVMContext: We need multiple
LLVMContexts (one per module in the simplest case, but at least one per
thread), and the lifetime of each context depends on the execution path of
the JIT'd code. We would like to deallocate contexts once all modules
associated with them have