I'm looking for a good (comprehensive) doc about memory alignment in C++, typical approaches, differences between compilers, and common pitfalls. Just to check if my understanding of the topic is correct and to learn something new.
This question is inspired by my answer to another question where I used following construct:
char const buf[1000] = ...;
unsigned int i = *reinterpret_cast<unsigned int*>(buf + shift); // shift can be anything
It was criticized as not conforming to memory alignment rules. Can you please explain as a bonus why this approach is flawed from memory alignment point of view? An example when it doesn't work will be highly appreciated. I know it's a bad approach in general, but I often use it in network protocol implementations, so it's more a practical question than theoretical one.
Also please don't mention strict-aliasing here, it's for another question.
Non-heap-allocated arrays of char
have no specific requirements on their alignment. So your buffer of a thousand characters could be on an odd offset. Trying to read an int
from that offset (reinterpreted as an int pointer obvious) would either result in poor performance or even a bus error on some hardware if the compiler doesn't split it up into separate read+bitmask operations.
Heap-allocated arrays of char
are guaranteed to be aligned suitably to store any object type, so this is always an option.
For non-heap based storage, use boost::aligned_storage
which ensures that the space is aligned properly for general use.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With