Where does nativeGetUninitializedObject actually exist?

前端 未结 2 968
-上瘾入骨i
-上瘾入骨i 2021-01-19 20:05

I was curious about some serialization stuff so I went poking around FormatterServices and found a method called nativeGetUninitializedObject that

相关标签:
2条回答
  • 2021-01-19 20:30

    The method exists in the CLR. The JIT compiler has access to a table inside the CLR that contains the addresses of all MethodImplOptions.InternalCall functions. The section of the table that's relevant to your question looks like this in the SSCLI20 source code (clr/src/vm/ecall.cpp):

    FCFuncStart(gSerializationFuncs)
        FCFuncElement("nativeGetSafeUninitializedObject", ReflectionSerialization::GetSafeUninitializedObject)
        FCFuncElement("nativeGetUninitializedObject", ReflectionSerialization::GetUninitializedObject)
    FCFuncEnd()
    

    To jit the method call, it merely looks up the function name in that table and generates a direct CALL instruction to the function address as listed in the table. Very fast, direct transition from managed code to code written in C++ inside the CLR.

    The ReflectionSerialization::GetUninitializedObject() method lives inside clr/src/vm/reflectioninvocation.cpp, it's too big to post here. You can have a look-see at the downloadable SSCLI20 source code. There's a bunch of error checking, then a call to a raw Allocate() method to allocate the memory for the object. No constructor call.

    0 讨论(0)
  • 2021-01-19 20:45

    This method actually exists in the native portion of the CLR. The MethodImplOptions.InternalCall signifies a call which is forwarded to the CLR native code and is implemented there.

    From MSDN:

    Specifies an internal call. An internal call is a call to a method that is implemented within the common language runtime itself.

    0 讨论(0)
提交回复
热议问题