This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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: [c++0x] std::thread fixes

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: Chris Fairles <chris dot fairles at gmail dot com>
Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, libstdc++ <libstdc++ at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Thu, 22 Jan 2009 19:37:22 +0100
Subject: Re: [c++0x] std::thread fixes
References: <4348dea50901211542p24118c39tcd0f30c37d5297b2@mail.gmail.com> <4978B384.4080207@oracle.com> <fac6bb500901221027v538da733ob7ac888573a3537e@mail.gmail.com>

Chris Fairles wrote:
> Most of these changes were previously discussed via private email and
> on the list as well. As for the ABI, I don't see the gnu.ver changes
> for the __start_thread  to _M_start_thread change and
> _Thread_data_base rename as well.
To be clear: when, in v3 we say ABI, we don't mean only the exports from
the .so, we mean in general anything potentially affecting
interoperability between objects built with old and new library headers.
Thus, for example, changing the size or the layout of a class of the
library usually breaks the ABI (unless is only inside the .so and not
visible externally). This is not so strict of course for the
experimental C++0x features, but, for instance, adding or removing a
member from std::vector would be an *extremely* serious bug. There is
something in the docs too.

Paolo.

References:
- [c++0x] std::thread fixes
  - From: Jonathan Wakely
- Re: [c++0x] std::thread fixes
  - From: Paolo Carlini
- Re: [c++0x] std::thread fixes
  - From: Chris Fairles

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