Displaying 3 results from an estimated 3 matches for "l188".
Did you mean:
188
2020 Jun 09
2
Implementing a VTable in LLVM
...bounds %Foo, %Foo* %1, i32 0, i32 0
store %_VtableFoo* @_VtableFoo, %_VtableFoo** %2
The issue is when it comes to actually calling the method. Up to this point, the code generates the expected IR (https://github.com/mukul-rathi/bolt/blob/vtable/src/llvm-backend/llvm_ir_codegen/expr_codegen.cc#L188:L202 <https://github.com/mukul-rathi/bolt/blob/vtable/src/llvm-backend/llvm_ir_codegen/expr_codegen.cc#L188:L202>)
%5 = load %Foo*, %Foo** %_var_y0
%6 = getelementptr inbounds %Foo, %Foo* %5, i32 0, i32 0
%7 = load %_VtableFoo*, %_VtableFoo** %6
%8 = getelementptr inbounds %_VtableF...
2020 May 21
2
on division of __int128 bit integer
Hi Team,
I observer that division of __int128 bit is very heavy operation.
It internally call a routine '__udivti3', which internally call '
__udivmodti4'.
Due to it the overall performance is much much slower (almost 15 time
slower than if I do it via a combination of 64-bit or microsoft '_udiv128').
Also what to know if I can directly call below routine directly from
2007 Nov 14
10
[GE users] Apple Leopard has dtrace -- anyone used the SGE probes/scripts yet?
Hi,
Chris (cc) and I try to get the SGE master monitor work with Apple Leopard
dtrace. Unfortunately we are stuck with the error msg below.
Anyone having an idea what could be the cause? What I can rule out as
cause is function inlining for the reasons explained below.
Background information on SGE master monitor implementation is under
http://wiki.gridengine.info/wiki/index.php/Dtrace