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?
On Sun, Jan 10, 2010 at 08:58:47AM -0800, Patrick Horgan wrote:
> Andrew Haley wrote:
> > On 01/10/2010 12:39 PM, Andreas Schwab wrote:
> >
> >> Andrew Haley <aph@redhat.com> writes:
> >>
> >>
> >>> Why do you say the effective type is different?
> >>>
> >> 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. That is
> > clearly the assumption on which the code relies.
> >
> But in the new compilers it's an integer type, not a character
> type--from the spec:
A character type is an integer type, so it is quite possible for
uint8_t to qualify both as a character type and as an integer type.
--
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se