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: possible structure layout bug


On Wed, 2004-06-09 at 20:44, Richard Henderson wrote:
> On Wed, Jun 09, 2004 at 06:22:24PM +0100, Stephen Kennedy wrote:
> > Normally, compilers place members from derived classes starting at
> > sizeof(base), but gcc breaks this rule if the class contains a simd type
> > and places the derived member in the padding of the base class.
> 
> Has nothing to do with simd or not.  Has everything to do 
> with POD or non-POD type.

Ok, so if I have this correct, POD members padding may not be reused by
derived classes but non-POD classes may have their padding reused.

Why then is __m128 not considered a POD type? It is most natural to
think of machine native register types as POD.

Stephen.
-- 
Stephen Kennedy stephen.kennedy@havok.com http://www.havok.com/ 
Game Developer Frontline Award Winner 2002 & 2003
Computer Graphics World 2003 Innovation Award Winner


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