Displaying 2 results from an estimated 2 matches for "invokeinterface".
2015 May 31
4
[LLVMdev] Hash Table Virtual Calls with Conflict Resolution Stubs
...placed in the vtable and
the hidden value will simply be ignored in those cases. Hence in
general the only overhead versus a C++ virtual call is setting the
hidden value, which is essentially a negligible cost. For more detail,
the basic elements of the virtual call mechanism are described in
'Invokeinterface Considered Harmless' [2] (albeit for Java).
---- Encoding calls in LLVM IR ----
Encoding this information in LLVM IR seems to be very difficult,
albeit I've noticed some recent developments (such as musttail) that
could be useful for this. There was a previous discussion of this
issue in...
2008 May 13
6
[LLVMdev] Iterator protocols
This is related to the general question of efficiency of unwinds. I'm
mulling over whether to use the Java-style or Python-style iterator
protocol for my language. The Python style is to have a special
exception (StopIteration) that is thrown when the end of the sequence is
reached. The Java style is to have a separate "hasNext" method on the
iterator object that says whether or