What exactly is an ‘aligned pointer’?

by

It means that the address being pointed at is evenly divisible by some factor.

Sometimes the term “natural alignment” is used, which generally means that objects having natural alignment need to be placed at addresses that are evenly divisble by the object’s size.

Alignment is somestimes very important, since many hardware-related things place restrictions on such alignment.

For instance, on the classic SPARC architecture (and also on classical ARM, I think), you can’t read an integer larger than one byte from an odd address. Trying to do so will immediately halt your program with a bus error. On the x86 architecture, the CPU hardware instead handles the problem (by doing multiple accesses to cache and/or memory as needed), although it might take longer. RISC:ier architectures typically don’t do this for you.

Things like these can also affect padding, i.e. the insertion of dummy data between e.g. structure fields in order to maintain alignment. A structure like this:

struct example
{
  char initial;
  double coolness;
};

would very likely end up having 7 bytes of padding between the fields, to make the double field align on an offset divisible by its own size (which I’ve assumed to be 8).

When viewed in binary, an address aligned to n bytes will have its log2(n) least-significant bits set to zero. For instance, an object that requires 32-byte alignment will have a properly-aligned address that ends with (binary) 00000, since log2(32) is 5. This also implies that an address can be forced into alignment by clearing the required number of bits.

More Related Contents:

  1. Why is integer assignment on a naturally aligned variable atomic on x86?
  2. How to solve the 32-byte-alignment issue for AVX load/store operations?
  3. Compelling examples of custom C++ allocators?
  4. How is the size of a C++ class determined?
  5. Memory alignment in C-structs
  6. Making std::vector allocate aligned memory
  7. Do class/struct members always get created in memory in the order they were declared?
  8. How is a vector’s data aligned?
  9. Atomicity in C++ : Myth or Reality
  10. When extending a padded struct, why can’t extra fields be placed in the tail padding?
  11. Double alignment
  12. how does malloc understand alignment?
  13. Questions about Hinnant’s stack allocator
  14. Aligning static string literals
  15. Memory alignment : how to use alignof / alignas?
  16. What is the recommended way to align memory in C++11
  17. Is it always the case that sizeof(T) >= alignof(T) for all object types T?
  18. Do I really have to worry about alignment when using placement new operator?
  19. std::tuple memory alignment
  20. Why does C++ disallow anonymous structs?
  21. Debug vs Release in CMake
  22. How to initialize a const field in constructor?
  23. Why can’t you use offsetof on non-POD structures in C++?
  24. Aliasing T* with char* is allowed. Is it also allowed the other way around?
  25. How to get the GL library/headers?
  26. How can I get the maximum or minimum value in a vector?
  27. Why does C++ parameter scope affect function lookup within a namespace?
  28. When did C++ compilers start considering more than two hex digits in string literal character escapes?
  29. What is the simplest way to convert char[] to/from tchar[] in C/C++(ms)?
  30. Literal initialization for const references

Leave a Comment