This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/37762] Member variable of empty base optimized (EBO) class appears on wrong offset
- From: "pinskia at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Oct 2008 10:45:48 -0000
- Subject: [Bug c++/37762] Member variable of empty base optimized (EBO) class appears on wrong offset
- References: <bug-37762-16792@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from pinskia at gmail dot com 2008-10-07 10:45 -------
Subject: Re: Member variable of empty base optimized (EBO) class appears on
wrong offset
Iirc there are some pod vs non pod issues here dealing wit padding and
the c++ standard and not even the abi.
Sent from my iPhone
On Oct 7, 2008, at 2:31 AM, "david dot rosenborg at pantor dot com"
<gcc-bugzilla@gcc.gnu.org
> wrote:
>
>
> ------- Comment #3 from david dot rosenborg at pantor dot com
> 2008-10-07 09:31 -------
> Ah, no, I wasn't aware of that document. I just thought that gcc was
> treating
> the Good and Bad cases inconsitently.
>
> Now, in layman's terms, is the reason for the padding that no two
> distinct
> instances of Empty may share the same address? If that is the case,
> it would
> explain the padding and this is not a bug.
>
> Sorry, should have investigated more before hitting the commit button.
>
> /David
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37762
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37762