RE: Double abstract class Inheritance concern.

RE: Double abstract class Inheritance concern.

[Chris Lattner]

Tiago Stein wrote:
> class A{};
> class B :public A{};
> class C: public A{ int g; };
> class D: public B, public C {
>   unsigned int foo;
> };
> Why sizeof class D is 12? Should not be 8?

I believe the reason is that the ABI does not permit multiple different
instances of A to be located at the same address, even if they have zero
size.  If the size of the structure was 8, all of "A", "B", and "A" would
have offset zero.

I'm not sure WHY this is required, but this is the reason it happens at
least.  A declaration of "A X[100];" allocates 100 bytes as
a result of the same rule.

-Chris

-- 
http://llvm.cs.uiuc.edu/
http://www.nondot.org/~sabre/Projects/

Re: Double abstract class Inheritance concern.

[Nathan Sidwell]

Chris Lattner wrote:
> Tiago Stein wrote:
> 
>>class A{};
>>class B :public A{};
>>class C: public A{ int g; };
>>class D: public B, public C {
>>  unsigned int foo;
>>};
>>Why sizeof class D is 12? Should not be 8?
> 
> 
> I believe the reason is that the ABI does not permit multiple different
> instances of A to be located at the same address, even if they have zero
> size.  If the size of the structure was 8, all of "A", "B", and "A" would
> have offset zero.
> 
> I'm not sure WHY this is required, but this is the reason it happens at
> least.  A declaration of "A X[100];" allocates 100 bytes as
> a result of the same rule.

It is a C++ language requirement that no two logically distinct objects
of the same type have the same address.

BEWARE. GNU C has an empty struct extension to C, that does not obey
the same rules.

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk

Re: Double abstract class Inheritance concern.

[Joe Buck]

Chris Lattner wrote:
> > I believe the reason is that the ABI does not permit multiple different
> > instances of A to be located at the same address, even if they have zero
> > size.  If the size of the structure was 8, all of "A", "B", and "A" would
> > have offset zero.
> > 
> > I'm not sure WHY this is required, but this is the reason it happens at
> > least.  A declaration of "A X[100];" allocates 100 bytes as
> > a result of the same rule.

On Mon, Mar 29, 2004 at 08:57:17AM +0100, Nathan Sidwell wrote:
> It is a C++ language requirement that no two logically distinct objects
> of the same type have the same address.

However, g++ still finds plenty of opportunities to allocate zero bytes
for a struct/class object, when it is not adjacent to any other objects of the
same type (e.g. an empty base class, or an empty data member of a struct
or class).

Double abstract class Inheritance concern.

[Tiago Stein]

Hy! I have  question concerning inheritance of empty classes.

Supose that I have:

Class A{

};

Class B: public A{
  unsigned int foo1;
};

because of C++ constraints on object sizes.. sizeof(A) is  4 (I am in a
32bit PC).


In class B, due to the attribute.. this extra size form A is supressed. So
sizeof B= 4 too..


Until here everything is OK, but... given:


class A{
};

class B :public A{
};


class C: public A{
 int g;
};

class D: public B, public C
{
  unsigned int foo;
};


Why sizeof class D is 12? Should not be 8? Why the extra size from the
empty classes is not eliminated this time? Is this due to any rules in the
standard? I passed hours looking for it but found nothing that could
obligate so.  This behavior is causing some real nasty side-effects in our
operating system due to memory restrictions in our embedded targets.


So, can someone explain me why of this? Maybe I am leaving something wrong
pass at my design if there is any rule that dictates this behavior.

Thanks for any help.

Re: Double abstract class Inheritance concern.

[Alexandre Oliva]

On Mar 28, 2004, Tiago Stein <tiago@lisha.ufsc.br> wrote:

> class A{ };
> class B :public A{ };
> class C: public A{ int g; };
> class D: public B, public C { unsigned int foo; };

> Why sizeof class D is 12? Should not be 8? Why the extra size from the
> empty classes is not eliminated this time? Is this due to any rules in the
> standard?

D::B::A and D::C::A must have different addresses.

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}