[Post] Will you use sizeof? (VC) kernelhao (original)

[Post] Will you use sizeof? (VC) kernelhao (original)Published by: 11:55:52 Source: yourblog.org)

This article consists of two parts. The first part focuses on how to use sizeof in VC to find the structure size and problems that are prone to, and provides solutions to the problems, the second part summarizes the main usage of sizeof in VC.

1. Structure of sizeof applications

See the following structure:

Struct mystruct

{

Double dda1;

Char DDA;

Int type

};

What will happen if sizeof is used for the structure mystruct? What is sizeof (mystruct? You may ask:

Sizeof (mystruct) = sizeof (double) + sizeof (char) + sizeof (INT) = 13

However, when the above structure is tested in VC, you will find that sizeof (mystruct) is 16. Do you know why such a result is obtained in VC?

In fact, this is a special processing of variable storage by VC. To increase the CPU storage speed, VC performs "alignment" on the starting addresses of some variables. By default, VC specifies that the offset of the starting address of each member variable to the starting address of the structure must be a multiple of the bytes occupied by the variable type. Common alignment types are listed below (vc6.0, 32-bit system ).

Type
Alignment (offset of the starting address of the variable to the starting address of the structure)

Char
The offset must be a multiple of sizeof (char), that is, 1.

Int
The offset must be a multiple of sizeof (INT), that is, 4.

Float
The offset must be a multiple of sizeof (float), that is, 4.

Double
The offset must be a multiple of sizeof (double), that is, 8.

Short
The offset must be a multiple of sizeof (short), that is, 2.

When each member variable is stored, the space is requested in sequence based on the order in which the structure appears, and the positions are adjusted according to the alignment above. The vacant byte VC is automatically filled. At the same time, to ensure that the size of the structure is a multiple of the number of byte boundary values of the structure (that is, the number of bytes occupied by the Type occupying the maximum space in the structure, therefore, after applying for space for the last member variable, the vacant bytes will be automatically filled as needed.

The following uses the previous example to illustrate how VC stores the structure.

Struct mystruct

{

Double dda1;

Char DDA;

Int type

};

When allocating space for the above structure, VC allocates space for the first member dda1 according to the sequence and alignment of the member variables, the starting address is the same as the starting address of the structure (the offset 0 is just a multiple of sizeof (double). The member variable occupies eight bytes; next, allocate space for the second member DDA. the offset of the next address that can be allocated to the starting address of the structure is 8, which is a multiple of sizeof (char, therefore, the DDA is stored in an alignment where the offset is 8. This member variable occupies sizeof (char) = 1 byte, and then allocates space for the third member type, in this case, the offset of the next allocable address to the starting address of the structure is 9, not a multiple of sizeof (INT) = 4. To meet the offset constraints of alignment, VC automatically fills in three bytes (these three bytes do not have anything). At this time, the next address that can be allocated has a 12 offset to the starting address of the structure, which is exactly sizeof (INT) = a multiple of 4, so the type is stored in the biased When the shift is 12, the member variable occupies sizeof (INT) = 4 bytes. At this time, the member variables in the entire structure have been allocated space, and the total occupied space is: 8 + 1 + 3 + 4 = 16, which is exactly the number of bytes in the structure (that is, the number of bytes occupied by the Type occupying the maximum space in the structure sizeof (double) = 8) so there is no vacant byte to fill. Therefore, the size of the entire structure is sizeof (mystruct) = 8 + 1 + 3 + 4 = 16. Among them, three bytes are automatically filled by VC and nothing makes sense.

Next, let's take another example to change the position of the member variable of mystruct above to the following:

Struct mystruct

{

Char DDA;

Double dda1;

Int type

};

How much space does this structure occupy? In the vc6.0 environment, we can obtain that sizeof (mystruc) is 24. Based on the space allocation principles mentioned above, we will analyze how VC allocates space for the above structure. (Simple description)

Struct mystruct

{

Char DDA; // The offset is 0. The alignment is satisfied and the DDA occupies 1 byte;

Double dda1; // the offset of the next available address is 1, not sizeof (double) = 8

// Multiple. You need to add 7 bytes to make the offset 8 (the alignment is satisfied ).

// Method). Therefore, VC automatically fills in 7 bytes, and dda1 is stored at an offset of 8

// Address, which occupies 8 bytes.

Int type; // the offset of the next available address is 16, which is twice that of sizeof (INT) = 4.

// Number, which meets the alignment of int, so no VC auto-fill is required.

// Put the address at the offset of 16, which occupies 4 bytes.

}; // All member variables are allocated space. The total size of the space is 1 + 7 + 8 + 4 = 20, not a structure.

// Number of knots (that is, the number of bytes occupied by the largest space type in the structure sizeof

// (Double) = 8), so four bytes need to be filled to meet the structure size

// Sizeof (double) = a multiple of 8.

Therefore, the total size of this structure is: sizeof (mystruc) is 1 + 7 + 8 + 4 + 4 = 24. Among them, 7 + 4 = 11 bytes are automatically filled by VC, and nothing makes sense.

The special processing of the structure storage by VC does increase the speed of the CPU storage variable, but sometimes it also brings some trouble. We also shield the default alignment of the variables, you can set the alignment of variables.

# Pragma pack (n) is provided in VC to set the variable to n-byte alignment. N-byte alignment means the offset of the Start address of the variable. First, if n is greater than or equal to the number of bytes occupied by the variable, the offset must meet the default alignment mode, second, if n is less than the number of bytes occupied by the variable type, the offset is a multiple of N, and the default alignment is not required. The total size of the structure also has a constraint, which is divided into the following two cases: if n is greater than the number of bytes occupied by all member variable types, the total size of the structure must be a multiple of the space occupied by the largest variable;

Otherwise, it must be a multiple of N. The following is an example of its usage.

# Pragma pack (push) // save alignment status

# Pragma pack (4) // set to 4-byte alignment

Struct Test

{

Char M1;

Double M4;

Int m3;

};

# Pragma pack (POP) // restore alignment

The size of the above structure is 16. Next we will analyze its storage situation. First, we will allocate space for M1, and its offset is 0, which meets our own alignment (4-byte alignment ), m1 occupies 1 byte. Then we start to allocate space for M4. At this time, the offset is 1 and three bytes need to be supplemented. In this way, the offset must be a multiple of N = 4 (because sizeof (double) is greater than N ), m4 occupies 8 bytes. Then allocate space for M3. At this time, the offset is 12, which must be a multiple of 4. m3 occupies 4 bytes. At this time, space has been allocated for all member variables. A total of 16 bytes are allocated, which is a multiple of N. If you change # pragma pack (4) to # pragma pack (16), the size of the structure is 24. (Please analyze it by yourself)

2. sizeof usage Summary

In VC, sizeof has many usage and may cause some errors. Next, we will summarize the usage of sizeof based on the parameters following sizeof.

A. the parameter is a data type or a common variable. For example, sizeof (INT) and sizeof (long. In this case, it should be noted that the results of different system systems or compilers may be different. For example, the int type occupies 2 bytes in a 16-bit system and 4 bytes in a 32-bit system.

B. the parameter is an array or pointer. The following is an example.

Int A [50]; // sizeof (A) = 4*50 = 200; calculates the space occupied by the array.

Int * A = new int [50]; // sizeof (A) = 4; A is a pointer, and sizeof (a) is a pointer.

// The size of a 32-bit system, of course, 4 bytes.

C. The parameter is a structure or class. The processing of sizeof applications in the class and structure is the same. However, there are two points to note: first, static members in the structure or class do not affect the size of the structure or class, because the storage location of static variables is irrelevant to the instance address of the structure or class.

Second, the structure without member variables or the size of the class is 1, because each structure or class must be guaranteed

Each instance has a unique address in the memory.

The following is an example,

Class test {int A; static double c}; // sizeof (TEST) = 4.

Test * s; // sizeof (S) = 4, and S is a pointer.

Class test1 {}; // sizeof (test1) = 1;

D. The parameter is other. The following is an example.

Int func (char s [5]);

{

Cout <sizeof (s); // here, 4 is output. Originally, s is an array,

// When a number parameter is passed, the system processes it as a pointer

// Calculate the pointer Size Based on sizeof (s.

Return 1;

}

Sizeof (func ("1234") = 4 // because the return type of func is int, it is equivalent

// Calculate sizeof (INT ).

The above is the basic usage of sizeof. In actual use, pay attention to the analysis of the allocation policy of VC allocation variables, so as to avoid some errors.

Source: http://www.csdn.net/develop/Read_Article.asp? Id = 26437