3 ms·
> In the Java section I also show inline caching, a standard optimization approach. Thanks. Does the CLR do inline caching for interface calls which cannot be
by chrisseaton 8y ago
> In the Java section I also show inline caching, a standard optimization approach.
Thanks. Does the CLR do inline caching for interface calls which cannot be devirtualised without speculation? Or not because of the lack of deoptimisation? Or does it have self-modifying code instead?
- pjmlp 8y agoIt depends very much of which .NET runtime we talk about (NGEN, Pre-RyuJIT, RyuJIT, IL2CPP, Mono, MDIL, .NET Native, .NET Core, Burst), and which version of it.
- latk 8y agoCLR routes any interface calls through an indirect cell or pad that can be quickly rewritten to point to a different dispatch stub. Some stubs perform caching whereas the generic resolver behaves as explained by the pseudocode in my article. The “book of the runtime” has a graph visualizing these possibilities: https://github.com/dotnet/coreclr/blob/master/Documentation/botr/virtual-stub-dispatch.md#stubs https://github.com/dotnet/coreclr/blob/master/Documentation/... So this is a self-modifying code approach.