3 ms·
Unless the compiler can prove you're never going to run into that case, it can't remove the call, and because the call is an imported function it still has to c
by userbinator 8y ago
Unless the compiler can prove you're never going to run into that case, it can't remove the call, and because the call is an imported function it still has to create the import and have an entry in the IAT for it, so it needs to be resolved at load time. Not all that surprising IMHO.
- ascar 8y agoThe author even said "we immediately knew what to do", which is kinda the contrary of surprising. The interesting bit is not that a slow loading dependency got imported anyway, but why that dependency is slow and that it can get imported very easily indirectly.