This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PR 17949 (unaligned memory accesses due to ivopts) question

From: Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>
To: gcc at gcc dot gnu dot org
Date: Sat, 16 Oct 2004 22:53:52 +0200
Subject: Re: PR 17949 (unaligned memory accesses due to ivopts) question
References: <20041016193534.GA15855@atrey.karlin.mff.cuni.cz> <20041016203741.GA22759@nevyn.them.org>

Hello,

> Well, a.f ought to be a pointer to unaligned integer.  Don't you get
> some kind of warning for this?

no.  There is -Wcast-align (disabled by default), but it does not
trigger in this case.  -Wpacked (also disabled by default) announces
that "packed attribute causes inefficient alignment for 'i'"
(but does not mention f; umm...).  And that's it, these are all warnings
that are triggered by STRICT_ALIGNMENT.

Zdenek

References:
- PR 17949 (unaligned memory accesses due to ivopts) question
  - From: Zdenek Dvorak
- Re: PR 17949 (unaligned memory accesses due to ivopts) question
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]