Displaying 3 results from an estimated 3 matches for "llv8".
Did you mean:
llv
2015 Nov 17
3
llvm.experimental.gc.statepoint genarates wrong Stack Map (or does it?)
...he deopt information for? Do you have a
>>> language runtime which supports deoptimization? Or are you using it
>>> for something different? If so, what? I'm curious to know how others
>>> are using the infrastructure.
>>
>> Sure.
>> I am working on LLV8, which is an attempt to use LLVM MCJIT as a
>> backend
>> for Google V8. So yes, we have a language runtime which supports
>> deoptimization.
>> Deoptimization support wasn't hard. We use the stackmap intrinsic for
>> that. (And we've encountered each type of...
2015 Nov 16
2
llvm.experimental.gc.statepoint genarates wrong Stack Map (or does it?)
...cified?
> Can I ask what you're using the deopt information for? Do you have a
> language runtime which supports deoptimization? Or are you using it
> for something different? If so, what? I'm curious to know how others
> are using the infrastructure.
Sure.
I am working on LLV8, which is an attempt to use LLVM MCJIT as a backend
for Google V8. So yes, we have a language runtime which supports
deoptimization.
Deoptimization support wasn't hard. We use the stackmap intrinsic for
that. (And we've encountered each type of Location except Direct so
far).
Now I am i...
2015 Nov 13
2
llvm.experimental.gc.statepoint genarates wrong Stack Map (or does it?)
Hello, list
I am not quite sure if what I'm experiencing is a bug or intentional
behavior.
In the code below the result of a function call is a deopt arg to
llvm.experimental.gc.statepoint
(http://llvm.org/docs/Statepoints.html#llvm-experimental-gc-statepoint-intrinsic).
Therefore a Stack Map containing location of this variable is created
upon code generation.
Here's the complete