Question

Does this code violate strict aliasing?

struct {int x;} a;
*(int*)&a = 3

More abstractly, is it legal to cast between different types as long as the primitive read/write operations are type correct?

Answer 1

First, it is legal to cast in C. §6.7.2.1/13:

Within a structure object, the non-bit-field members and the units in
which bit-fields reside have addresses that increase in the order in
which they are declared. A pointer to a structure object, suitably
converted, points to its initial member (or if that member is a
bit-field, then to the unit in which it resides), and vice versa.
There may be unnamed padding within a structure object, but not at its
beginning.

The aliasing rule reads as follows (§6.5/7):

An object shall have its stored value accessed only by an lvalue expression that has one of
the following types:

• a type compatible with the effective type of the object,
• a qualified version of a type compatible with the effective type of the object,
• a type that is the signed or unsigned type corresponding to the effective type of the
  object,
• a type that is the signed or unsigned type corresponding to a qualified version of the
  effective type of the object,
• an aggregate or union type that includes one of the aforementioned types among its
  members (including, recursively, a member of a subaggregate or contained union), or
• a character type.

Here you would be accessing it via pointers of a “type compatible with the effective type of the object” and “an aggregate or union type that includes one of the aforementioned types among its members”, so no problem with aliasing either. So in C, it is indeed perfectly legal to access the first member of a structure by casting the pointer to the structure to the type of the member in question.

In C++, however, you’ll often find vtables and other things at the start of a C++ object. In your specific case, however, your structure is of standard layout, and so this is explicitly allowed (§9.2/20 in n3290, thanks Luc Danton! – C++03 apparently has a similar rule, expressed in terms of POD objects).