• <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>
            asm, c, c++ are my all
            -- Core In Computer
            posts - 139,  comments - 123,  trackbacks - 0

            /********************************************\
            |????歡迎轉載, 但請保留作者姓名和原文鏈接, 祝您進步并共勉!???? |
            \********************************************/


            C++對象模型(13) - 3.5 Object Member Efficiency
            作者: Jerry Cat
            時間: 2006/11/17
            鏈接:?
            http://m.shnenglu.com/jerysun0818/archive/2006/11/17/15311.html


            3.5 Object Member Efficiency
            ;-----------------------------------------------------------------------

            An obvious observation is that without the optimizer turned on, it is extremely difficult to guess at the performance characteristics of a program, since the code is potentially hostage to the "quirk(s) of code generation…unique to a particular compiler." Before one begins source level "optimizations" to speed up a program, one should always do actual performance measurements rather than relying on speculation and common sense.不要想當然, 要試驗之.

            In the next sequence of tests, I introduced first a three-level single inheritance representation of the Point abstraction and then a virtual inheritance representation of the Point abstraction. I tested both direct and inline access (multiple inheritance did not fit naturally into the model, so I decided to forego it.) The general hierarchy is

            class Point1d {...};?????????????????????????? // maintains x
            class Point2d : public Point1d {...};???? // maintains y
            class Point3d : public Point2d {...};???? // maintains z

            The one-level virtual inheritance derived Point2d virtually from Point1d. The two-level virtual inheritance additionally derived Point3d virtually from Point2d. Table 3.2 lists the results of running the tests for both compilers. (Again, I break out the times for the two compilers only when their performances differ significantly from each other's.)

            Table 3.2. Data Access under Inheritance Models

            ???????????????????????????????????? Optimized?????? Non-optimized
            Single Inheritance
            ???? Direct Access?????????? 0.80???????????????? 1.42
            ???? Inline Methods
            ???? CC???????????????????????????0.80??????????????? 2.55
            ???? NCC????????????????????????0.80??????????????? 3.10
            ?
            Virtual Inheritance — 1-Level
            ???? Direct Access??????????? 1.60????????????? 1.94
            ???? Inline Methods
            ???? CC????????????????????????????1.60????????????? 2.75
            ???? NCC?????????????????????????1.60????????????? 3.30
            ?
            Virtual Inheritance — 2-Level
            ???? Direct Access
            ???? CC????????????????????????????2.25????????????? 2.74
            ??? ?NCC?????????????????????????3.04????????????? 3.68
            ?
            ??? Inline Methods
            ???? CC????????????????????????????2.25????????????? 3.22
            ???? NCC?????????????????????????2.50????????????? 3.81
            ?
            Single inheritance should not affect the test performance, since the members are stored contiguously within the derived class object and their offsets are known at compile time. The results, as expected, were exactly the same as those of the independent abstract data type. (The same should be true under multiple inheritance, but I didn't confirm that.)

            Again, it is worth noting that with the optimizer off, performance, which common sense says should be the same (direct member access versus inline access), is in practice slower in the case of inline functions. The lesson again is that the programmer concerned with efficiency must actually measure the performance of his or her program and not leave the measurement of the program to speculation and assumption. It is also worth noting that optimizers don't always work. I've more than once had compilations fail with an optimizer turned on that compiled fine "normally."別想當然, 實驗之! 編譯時盡可能打開優化開關.

            The virtual inheritance performance is disappointing in that neither compiler recognized that the access of the inherited data member pt1d::_x is through a nonpolymorphic class object and that therefore indirect runtime access is unnecessary. Both compilers generate indirect access of pt1d::_x (and pt1d::y in the case of two levels of virtual inheritance), even though its location within the two Point3d objects is fixed at compile time. The indirection significantly inhibited the optimizer's ability to move all the operations within registers. The indirection did not affect the non-optimized executables significantly.
            虛繼承導致性能大降, 即使打開優化開關也沒太大起色.

            posted on 2006-11-17 18:11 Jerry Cat 閱讀(733) 評論(0)  編輯 收藏 引用

            <2006年11月>
            2930311234
            567891011
            12131415161718
            19202122232425
            262728293012
            3456789

            常用鏈接

            留言簿(7)

            隨筆檔案

            最新隨筆

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            人妻无码αv中文字幕久久| 男女久久久国产一区二区三区| 丰满少妇人妻久久久久久| 国产精品久久一区二区三区| 久久WWW免费人成—看片| 麻豆精品久久久久久久99蜜桃| 亚洲综合熟女久久久30p| 国产高潮久久免费观看| 国产精品久久久香蕉| 国产成人久久激情91| 99精品久久精品一区二区| 国产精品久久久久久久午夜片| 亚洲中文精品久久久久久不卡| 久久精品国产一区二区三区| 亚洲国产精品久久久天堂| 亚洲国产精品无码久久久久久曰| 69国产成人综合久久精品| 久久精品国产亚洲AV香蕉| 久久无码国产| Xx性欧美肥妇精品久久久久久| 老色鬼久久亚洲AV综合| 国产69精品久久久久APP下载| 99热精品久久只有精品| 久久精品国产一区二区三区日韩| 亚洲精品NV久久久久久久久久 | 亚洲精品乱码久久久久久中文字幕| 亚洲国产精品久久久久久| 99re这里只有精品热久久| 香蕉久久久久久狠狠色| 亚洲欧美日韩久久精品| 日韩久久无码免费毛片软件 | 性欧美大战久久久久久久| 久久久久人妻精品一区三寸蜜桃| 久久精品国产亚洲网站| 91精品国产色综久久 | 精品多毛少妇人妻AV免费久久 | 亚洲国产精品成人AV无码久久综合影院| 97精品伊人久久久大香线蕉| 国产精品狼人久久久久影院| 久久本道综合久久伊人| 亚洲精品99久久久久中文字幕|