In the compiler group, we think about migration issues every day. We
have a plan for a future major release that will fix all known ABI bugs
and provide a new C++ standard library as well. (The C++ standard
library is part of the C++ ABI.)
A new C++ standard that will force binary incompatibility is planned for
release in 2009. We don't want to break the C++ ABI very often, so the
new standard will mark the dividing line between stable ABIs, just as
the 1998 standard (which also broke binary compatibility) was the
dividing line between the old stable ABI and the current stable ABI.
---
Steve Clamage, [EMAIL PROTECTED]
On 03/22/07 08:53, Bart Smaalders wrote:
Dan Price wrote:
On Thu 22 Mar 2007 at 08:44AM, [EMAIL PROTECTED] wrote:
If you run your two variants under truss -c, you may see that under CC
this seems to generate an excess of lseek's. I'm not sure why:
This is the problem with the default C++ library, I believe.
You're right. That works great.
But we like it when things go fast in the default. :) Is there
a bug open to correct this issue in the default C++ library?
-dp
Dan, you're absolutely right. This should be changed. Is someone
thinking about the migration issues? From the documentation:
Later versions of the compiler implemented the new language features.
However, in order to maintain binary compatibility with existing
object files, the macros in the libCstd headers were not modified. As
a result, the latest version of libCstd
continues to have some missing functionality and some of the functions
accept a different set of arguments than those that are specified in
the standard.
The libstlport library was introduced in the C++ 5.4 release and uses
all the language features needed by the library. No functionality in
the library is suppressed because of any missing
language features. As a result, the libstlport library conforms
much more closely to the standard than libCstd does.
- Bart
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
