The Hidden Bytes in your Structs

Have you ever checked the sizeof your structure and found that the numbers don't add up?

struct Data {
    char a; // 1 byte
    int b;  // 4 bytes
};
// You might expect 5, but sizeof(Data) is usually 8!

Why does this happen?

CPUs are optimized to read data from memory addresses that are "aligned" (multiples of 4 or 8). Reading an integer from address 1003 is much slower than reading it from address 1000. To keep the CPU happy, the C compiler adds invisible padding bytes between your variables to ensure they land on "good" addresses.

How to Save Memory

You can often shrink your structures by simply ordering your variables from largest to smallest.

• Bad: char, int, char, int (Lots of padding).
• Good: int, int, char, char (Minimal padding).

#pragma pack(1)

If you are sending data over a network or writing to a file format, you might want to disable padding entirely. This directive tells the compiler: "Do not add any padding, pack these bytes as tightly as possible."

Use the sizeof operator frequently during development to verify that your structures aren't ballooning in size due to hidden padding!