C++ Memory model和bit-field
C++设计的目的包括尽可能在语法上与C兼容,面向底层和上层等等,而内存模型和位域就是C++从C继承来的语法和特性之一。
ISO/IEC 14882 Programming languages C++在第六章,第十章对内存模型和位域进行了如下阐述:
标准
6.7.1 Memory model [intro.memory]
-
The fundamental storage unit in the C++ memory model is the byte. A byte is at least large enough to contain any member of the basic execution character set (5.3) and the eight-bit code units of the Unicode30 UTF-8 encoding form and is composed of a contiguous sequence of bits31, the number of which is implementation defined. The least significant bit is called the low-order bit; the most significant bit is called the high-order bit. The memory available to a C++ program consists of one or more sequences of contiguous bytes. Every byte has a unique address.
-
[Note 1 : The representation of types is described in 6.8. — end note]
-
A memory location is either an object of scalar type or a maximal sequence of adjacent bit-fields all having nonzero width.
[Note 2 : Various features of the language, such as references and virtual functions, can involve additional memory locations that are not accessible to programs but are managed by the implementation. — end note]
Two or more threads of execution (6.9.2) can access separate memory locations without interfering with each other. -
[Note 3 : Thus a bit-field and an adjacent non-bit-field are in separate memory locations, and therefore can be concurrently updated by two threads of execution without interference. The same applies to two bit-fields, if one is declared inside a nested struct declaration and the other is not, or if the two are separated by a zero-length bit-field declaration, or if they are separated by a non-bit-field declaration. It is not safe to concurrently update two bit-fields in the same struct if all fields between them are also bit-fields of nonzero width. — end note]
-
[Example 1 : A class declared as
contains four separate memory locations: The member a and bit-fields d and e.ee are each separate memory locations, and can be modified concurrently without interfering with each other. The bit-fields b and c together constitute the fourth memory location. The bit-fields b and c cannot be concurrently modified, but b and a, for example, can be. — end example]
11.4.10 Bit-fields [class.bit]
-
A member-declarator of the form
identifieropt attribute-specifier-seqopt : constant-expression brace-or-equal-initializeropt
specifies a bit-field. The optional attribute-specifier-seq appertains to the entity being declared. A bit-field shall not be a static member. A bit-field shall have integral or enumeration type; the bit-field semantic property is not part of the type of the class member. The constant-expression shall be an integral constant expression with a value greater than or equal to zero and is called the width of the bit-field. If the width of a bit-field is larger than the width of the bit-field’s type (or, in case of an enumeration type, of its underlying type), the extra bits are padding bits (6.8). Allocation of bit-fields within a class object is implementation-defined.
Alignment of bit-fields is implementation-defined. Bit-fields are packed into some addressable allocation unit.[Note 1 : Bit-fields straddle allocation units on some machines and not on others. Bit-fields are assigned right-to-left on some machines, left-to-right on others. — end note]
-
A declaration for a bit-field that omits the identifier declares an unnamed bit-field. Unnamed bit-fields are not members and cannot be initialized. An unnamed bit-field shall not be declared with a cv-qualified type.
[Note 2 : An unnamed bit-field is useful for padding to conform to externally-imposed layouts. — end note]
As a special case, an unnamed bit-field with a width of zero specifies alignment of the next bit-field at an allocation unit boundary. Only when declaring an unnamed bit-field may the width be zero.
-
The address-of operator & shall not be applied to a bit-field, so there are no pointers to bit-fields. A non-const reference shall not be bound to a bit-field (9.4.4).
[Note 3 : If the initializer for a reference of type **const T&**is an lvalue that refers to a bit-field, the reference is bound to a temporary initialized to hold the value of the bit-field; the reference is not bound to the bit-field directly. See 9.4.4. — end note]
-
If a value of integral type (other than bool) is stored into a bit-field of width N and the value would be representable in a hypothetical signed or unsigned integer type with width N and the same signedness as the bit-field’s type, the original value and the value of the bit-field compare equal. If the value true or false is stored into a bit-field of type bool of any size (including a one bit bit-field), the original bool value and the value of the bit-field compare equal. If a value of an enumeration type is stored into a bit-field of the same type and the width is large enough to hold all the values of that enumeration type (9.7.1), the original value and the value of the bit-field compare equal.
[Example 1 :
— end example]
6.7.1内存模型 [intro.memory.zh]
-
C++内存模型中的基本存储单元是 byte。byte (字节)的大小至少足够容纳基本执行字符集(basic execution character set (5.3) 的任何成员 和 由连续的比特序列组成的8-bit (8比特)单元的Unicode30 UTF-8编码形式31,其成员数量由实现定义。最不重要的位被称作低阶位(low-order bit);最重要的位被称作高阶位(high-order bit)。C++程序可用的内存是由一个或多个连续的字节序列组成的。每个字节都有一个唯一的地址。
-
[Note 1 : 对类型的描述在6.8. — end note]
-
内存位置(memory location)要么是标量类型的对象,要么是相邻位域的最大序列,它们都具有非零宽度。
[Note 2 : 语言的各种特性,如引用和虚函数,可能涉及到程序无法访问的额外内存位置,但由实现管理。 — end note]
两个或更多的执行线程 (6.9.2) 可以访问独立的内存位置,而不会相互干扰。
-
[Note 3 : 因此,位域和相邻的非位域是在不同的内存位置,因此可以由两个执行线程同时更新而不发生干扰。这同样适用于两个位域,如果一个被声明在嵌套结构体声明中,而另一个没有,或者两者被零长度的位域声明分开,或者它们被非位域声明分开。如果同一结构体中的两个位域之间的所有位域也是宽度为非零的位域,那么同时更新这两个位域是不安全的。 — end note]
-
[Example 1 : 有如下声明的类
包含四个分开的内存位置:成员 a和位域 d和 e.ee都有不同的内存位置,可以由两个执行线程同时修改而不发生干扰。位域 b和 c共同构成了第四个内存位置。位域 b和 c不能同时修改,但是 b和 a,如上,可以。 — end example]
11.4.10 Bit-fields [class.bit.zh]
-
成员声明有如下形式
标识符可选 属性序列可选 : 常量表达式 花括号或等号初始化器 可选
定义一个位域。可选的属性序列属于被声明的实体。位域不应该是静态成员。位域应含有整数或者枚举,位域的语义属性不属于类成员。常数表达式应是值大于或等于0的整数常数表达式,并被称为位域的宽度。如果位域的宽度大于该位域类型的宽度(或者在枚举类型的情况下,大于其底层类型的宽度),那么额外的位是填充位 (6.8)。位域在类对象中的分配是由实现定义的。
位域的排列是由实现定义的。位域被打包到一些可寻址的分配单元中。[Note 1 : 位域在一些机器上跨越分配单元,而在另一些机器上不跨越。位域在一些机器上从右到左分配,在其他机器上从左到右分配。 — end note]
-
省略了标识符的位域声明是对未命名的位域的声明。未命名的位域不是成员,不能被初始化。未命名的位域不应该用cv限定来声明。
[Note 2 : 未命名的位域对于填充以符合外部强加的布局很有用。 — end note]
作为一种特殊情况,宽度为0的未命名的位域指定了下一个位域在分配单元边界进行对齐。只有在声明未命名的位域时,其宽度才可以为零。
-
取址运算符 & 不应该对位域使用,因为没有指向位域的指针。非常量引用不应该指向位域 (9.4.4)。
[Note 3 : 如果 const T& 类型的引用的初始化器是指向位域的lvalue,那么该引用被绑定到临时的初始化器上,以保持位域的值;该引用没有直接绑定到位域。参见9.4.4. — end note]
-
如果整数(和 bool 进行区分)被储存到了宽度为 N 的位域中,并且该值可以在假设的有符号或无符号的整数类型中表示,其宽度为 N,并且与该位域的类型具有相同的符号性,则原始值和位域的值比较相等。如果值 true or false 被存储到任何大小的bool类型的位域中(包括一个比特的位域),原bool值和位域的值比较相等。如果枚举类型的值被存储到同一类型的位域中,并且其宽度足以容纳该枚举类型的所有值 (9.7.1),那么原始值和位域的值比较相等。
[Example 1 :
— end example]
总结
虽然标准什么都说了,但是好像又没说什么,所以参考cppreference总结如下:
概述
bit-field是用于极限压缩内存使用而诞生的特性,其通过按字节定义数据大小来进行内存高效利用:
这个结构体中b1,b2,b3可以认为使用了同一块内存,因为C++内存是以字节来划分的,而这3个变量不能按字节划分出独立的内存序列区域。
在并发中,只有对不同的独立字节序列进行修改才能保证安全,而bit-field不保证这一点。
改进版的代码是使用 : 0 来强迫后面的变量使用一块全新的字节序列作为储存空间,不去管之前的变量是否用完了之前储存空间所有的比特,仅具有对齐作用。
这时候b1就和b2,b3分离开,对b1和b2,b3分别进行并发修改是安全的。
位域成员和非位域成员可以混写,非位域成员对齐到下一个独立内存地址保证并发安全。
位域成员可以进行初始化和构造,允许大括号构造和等号构造。
注意事项
当指定一个int类型变量使用小于 sizeof(int) 个bit储存时,编译器会尽可能确保可以正确的表示一部分长度:
这个示例中,由于指定了使用8bit储存int的b1,所以编译器将8bit的最高位设置为符号位,于是最小可以储存 -128,最高能储存127。
如果数值不能储存到指定比特内,则由实现定义结果,例如msvc中,b1 = 128 == -128,129 == -127等,编译器会保证溢出不会影响其他共享内存地址的位域成员。