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: RFC: attribute "unpadded"

From: Mark Mitchell <mark at codesourcery dot com>
To: Richard Henderson <rth at redhat dot com>
Cc: Gabriel Dos Reis <gdr at integrable-solutions dot net>, Andreas Schwab <schwab at suse dot de>, Paul Koning <pkoning at equallogic dot com>, "aoliva at redhat dot com" <aoliva at redhat dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Thu, 29 Aug 2002 16:43:19 -0700
Subject: Re: RFC: attribute "unpadded"

--On Thursday, August 29, 2002 04:32:58 PM -0700 Richard Henderson <rth@redhat.com> wrote:

On Thu, Aug 29, 2002 at 03:27:21PM -0700, Mark Mitchell wrote:

Yes.  Most front ends (sample of 4) actually create both types, although
they do:

 struct A { void *__vptr; char c; };

rather than:

 struct A { struct __A body; }

I'm not sure if there's ever a case where that matters.

For type-based aliasing, it does matter.

Indeed, using the later form in the C++ front end would fix
the aliasing issues currently in the front end, would it not?

I will be cautious and just say that it would help.  There are
still some other issues, but you're right that it would be a
step in the right direction.

--
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com

References:
- Re: RFC: attribute "unpadded"
  - From: Richard Henderson

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