This is the mail archive of the gcc-help@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: g++ serious bug in Ubuntu Lucid Lynx

From: Alexey Salmin <alexey dot salmin at gmail dot com>
To: Ian Lance Taylor <iant at google dot com>
Cc: Christian Convey <christian dot convey at gmail dot com>, gcc-help at gcc dot gnu dot org
Date: Thu, 3 Jun 2010 10:31:32 +0700
Subject: Re: g++ serious bug in Ubuntu Lucid Lynx
References: <4C067E79.1050904@kldcompanies.com> <AANLkTikooC7b2KV1p9zTbeI-yZlBWzGWxTnv6TtOm3id@mail.gmail.com> <mcrr5kpgegn.fsf@dhcp-172-17-9-151.mtv.corp.google.com>

On Thu, Jun 3, 2010 at 7:14 AM, Ian Lance Taylor <iant@google.com> wrote:
> Christian Convey <christian.convey@gmail.com> writes:
>
>> Are you sure that's a bug in the legalistic sense? ?IIRC, C and C++
>> don't promise any particular memory layout for structs.
>
> They don't promise any particular memory layout, but gcc does promise
> that it will not arbitrarily change the layout in new releases. ?If it
> did, it would be impossible for code compiled by one version of gcc to
> call a function defined by a different version of gcc while passing a
> struct parameter.
>
> Ian

I always thought that structure layout conventions are plarform-wide
much like calling conventions. Otherwise, how can we link together
code compiled by different compilers?

Alexey

Follow-Ups:
- Re: g++ serious bug in Ubuntu Lucid Lynx
  - From: Christian Convey

References:
- g++ serious bug in Ubuntu Lucid Lynx
  - From: David R. Doucette
- Re: g++ serious bug in Ubuntu Lucid Lynx
  - From: Christian Convey
- Re: g++ serious bug in Ubuntu Lucid Lynx
  - From: Ian Lance Taylor

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