• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            天下

            記錄修行的印記

            Double Thunking


            By default, when compiling with /clr (not /clr:pure), the definition of a managed function causes the compiler to generate a managed entry point and a native 

            entry point. This allows the managed function to be called from native and managed call sites. However, when a native entry point exists, it can be the entry 
            point for all calls to the function. If a calling function is managed, the native entry point will then call the managed entry point. In effect, two calls 
            are required to invoke the function (hence, double thunking). For example, virtual functions are always called through a native entry point.
            One resolution is to tell the compiler not to generate a native entry point for a managed function, that the function will only be called from a managed 
            context, by using the __clrcall calling convention.
            Similarly, if you export (dllexport, dllimport) a managed function, a native entry point is generated and any function that imports and calls that function 
            will call through the native entry point. To avoid double thunking in this situation, do not use native export/import semantics; simply reference the 
            metadata via #using (see The #using Directive).
            In Visual C++ 2005 the compiler was updated to reduce unnecessary double thunking. For example, any function with a managed type in the signature (including 
            return type) will implicitly be marked as __clrcall. For more information on double thunk elimination, see 
            http://msdn.microsoft.com/msdnmag/issues/05/01/COptimizations/default.aspx.
            Example
            The following sample demonstrates double thunking. When compiled native (without /clr), the call to the virtual function in main generates one call to T's 
            copy constructor and one call to the destructor. Similar behavior is achieved when the virtual function is declared with /clr and __clrcall. However, when 
            just compiled with /clr, the function call generates a call to the copy constructor but there is another call to the copy constructor due to the 
            native-to-managed thunk.
            純 MSIL 程序集可以調用非托管函數,但不能由非托管函數調用。因此,與非托管函數使用的服務器代碼相比,純 MSIL 更適合于使用非托管函數的客戶端代碼。
            當我們使用/clr選項(不是/clr:pure)進行編譯的時候,一個托管函數(managed function),會導致編譯器生成一個托管的入口點(managed entry point)和一個原生的入口點
            (native entry point),這樣可以使得托管函數既可以被托管代碼調用,也可以被原生代碼調用。但是,當一個原生的入口點存在的時候,它將成為所有調用的入口點。也就是說
            如果調用者是托管的,它還是會先去調用原生入口點,然后原生的入口點再去調用托管的入口點,這就意味著調用了兩次函數入口點(Double Thunking)。 



            c++ cli 標準

            posted on 2015-12-01 11:14 天下 閱讀(335) 評論(0)  編輯 收藏 引用 所屬分類: C#

            <2015年12月>
            293012345
            6789101112
            13141516171819
            20212223242526
            272829303112
            3456789

            導航

            統計

            常用鏈接

            留言簿(4)

            隨筆分類(378)

            隨筆檔案(329)

            鏈接

            最新隨筆

            搜索

            最新評論

            国产精久久一区二区三区| 久久国产高潮流白浆免费观看| 久久99精品久久久久婷婷| 99久久精品费精品国产一区二区| 久久天天躁狠狠躁夜夜不卡| 久久婷婷色香五月综合激情| 国内精品久久久久影院薰衣草| 久久亚洲中文字幕精品有坂深雪 | 欧洲性大片xxxxx久久久| 久久青草国产精品一区| 久久久久亚洲精品男人的天堂| 无码专区久久综合久中文字幕| 777米奇久久最新地址| 久久毛片免费看一区二区三区| 久久亚洲AV成人无码电影| 久久综合九色综合精品| 久久伊人色| 亚洲国产精品久久久久| 一本色道久久综合狠狠躁篇 | 99久久精品国产一区二区| 久久久国产视频| 蜜桃麻豆www久久国产精品| 亚洲AV日韩AV天堂久久| 欧洲国产伦久久久久久久| 久久精品免费观看| 久久久免费精品re6| 久久夜色精品国产亚洲| 久久夜色撩人精品国产| 精品水蜜桃久久久久久久| 国产69精品久久久久9999| 国产精品女同一区二区久久| 国产亚洲综合久久系列| 亚洲成av人片不卡无码久久| 久久se精品一区二区影院 | 777午夜精品久久av蜜臀| 久久精品亚洲福利| 国产精品免费久久久久影院| 欧美综合天天夜夜久久| 91精品国产综合久久四虎久久无码一级| 无码国内精品久久人妻蜜桃| 久久AV高潮AV无码AV|