This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Sorry to mention aliasing again, but is the standard IN6_ARE_ADDR_EQUAL really wrong?
> ...
> >> The object type is uint8_t, but accessed as uint32_t. That is
> >> undefined.
> >
> > Unless uint8_t is a character type, as I understand it.
>
> In which way does it make a difference? For aliasing consideration,
> only the type of access matters.
The aliasing rules treat "char" specially because char is a bit like a
"poor main's void".
paul