• <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++對象模型(8) - Chapter 3. The Semantics of Data
            ?

            作者: Jerry Cat
            時間: 2006/11/15
            鏈接:?
            http://www.shnenglu.com/jerysun0818/archive/2006/11/15/15185.html


            ;-----------------------------------------------------------------------
            ;Chapter 3. The Semantics of Data
            ;-----------------------------------------------------------------------
            Chapter 3. The Semantics of Data - 空類不空

            class X {};
            class Y : public virtual X {};
            class Z : public virtual X {};
            class A : public Y, public Z {};
            None of these classes contains any explicit data—any anything, in fact, except an inheritance
            relationship—so he apparently believed the size of each class should be 0. It wasn't,
            of course—not even the apparently benign class X:

            sizeof X yielded 1
            sizeof Y yielded 8
            sizeof Z yielded 8
            sizeof A yielded 12
            Let's look at each declaration in turn and see what's going on. An empty class, such as

            // sizeof X == 1
            class X {};
            in practice is never empty. Rather it has an associated size of 1 byte—a char member inserted
            by the compiler. This allows two objects of the class, such as

            X a, b;
            if ( &a == &b ) cerr << "yipes!" << endl;//to be allocated unique addresses in memory.哈!

            // sizeof Y == sizeof Z == 8
            class Y : public virtual X{};
            class Z : public virtual X{};
            On his machine, the size of both classes Y and Z is 8. This size, however, is partially machine dependent. It also depends in part on the compiler implementation being used. The given size of both class Y and class Z on any machine is the interplay of three factors:

            (1). Language support overhead. There is an associated overhead incurred in the language support of virtual base classes. Within the derived class, this overhead is reflected as some form of pointer, either to the virtual base class subobject or to an associated table within which either the address or offset to the virtual base class subobject is stored. On my correspondent's machine, the pointer is 4 bytes. (Virtual base classes are discussed in Section 3.4.)

            (2). Compiler optimization of recognized special cases. There is the 1 byte size of the virtual base class X subobject also present within Y (and Z). Traditionally, this is placed at the end of the "fixed" (that is, invariant) portion of the derived class. Some compilers now provide special support for an empty virtual base class (the paragraph following item 3 discusses this in more detail). Our correspondent's compiler, however, did not provide this special handling.

            (3). Alignment constraints. The size of class Y (and Z) at this point is 5 bytes. On most machines, aggregate structures have an alignment constraint so that they can be efficiently loaded from and stored to memory. On my correspondent's machine, alignment of an aggregate is on a 4-byte boundary. So class Y (and Z) requires 3 bytes of padding. The result is a final size of 8.

            The C++ object model representation for nonstatic data members optimizes for space and access time (and to preserve compatibility with the C language layout of the C struct) by storing the members directly within each class object. This is also true for the inherited nonstatic data members of both virtual and nonvirtual base classes, although the ordering of their layout is left undefined. Static data members are maintained within the global data segment of the program and do not affect the size of individual class objects.(靜態數據成員被放在全局數據段, 并不影響單個類的大小)
            ?
            Only one instance of a static data member of a class exists within a program regardless of the number of times that class is an object of direct or indirect derivation. (The static data members of a template class behave slightly differently. See Section 7.1 for a discussion.)模板類的靜態數據成語有所不同

            類的大小讓你吃驚地"大"的原因來源于2方面:
            (1). Additional data members added by the compilation system to support some language functionality (primarily the virtuals)

            (2). Alignment requirements on the data members and data structures as a whole

            posted on 2006-11-15 16:55 Jerry Cat 閱讀(566) 評論(0)  編輯 收藏 引用

            <2006年6月>
            28293031123
            45678910
            11121314151617
            18192021222324
            2526272829301
            2345678

            常用鏈接

            留言簿(7)

            隨筆檔案

            最新隨筆

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            精品久久久无码人妻中文字幕豆芽| 久久91这里精品国产2020| 色欲久久久天天天综合网精品 | 伊色综合久久之综合久久| 国产亚洲精久久久久久无码AV| 99国产欧美精品久久久蜜芽| 72种姿势欧美久久久久大黄蕉| 久久国产免费观看精品| 久久国产精品免费一区二区三区| 久久精品国产72国产精福利| 中文字幕精品久久| avtt天堂网久久精品| 久久精品成人影院| 国产精品18久久久久久vr| 久久久亚洲精品蜜桃臀| 久久精品国产精品亚洲毛片 | 99久久国产综合精品网成人影院| 99久久婷婷国产综合精品草原| 色偷偷88欧美精品久久久| 久久天天日天天操综合伊人av| 久久综合狠狠综合久久综合88| 一级做a爱片久久毛片| 亚洲欧美国产精品专区久久 | 伊人久久综合精品无码AV专区| 国产精品毛片久久久久久久| 亚洲精品高清一二区久久| 久久66热人妻偷产精品9| 国产毛片久久久久久国产毛片| 97超级碰碰碰久久久久| 97久久国产综合精品女不卡| 中文字幕亚洲综合久久菠萝蜜| 久久免费视频观看| 久久99国产综合精品| 亚洲人成精品久久久久| 久久人人爽人人爽人人片AV麻豆 | 亚洲精品乱码久久久久久蜜桃| 久久青青草原综合伊人| 久久久久亚洲AV无码观看| 久久国内免费视频| 亚洲成av人片不卡无码久久| 久久综合九色综合久99|