[haiku-development] Re: GCC 5
- From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 7 Mar 2016 07:09:31 +0100
On Sun, Mar 06, 2016 at 07:28:32PM -0800, Chris Hanson wrote:
On Mar 4, 2016, at 10:34 PM, Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
wrote:
On Sat, Mar 05, 2016 at 03:37:02AM +0000, Alexander von Gluck IV wrote:
GCC 5 ships with a new C++ abi... is this going to cause us trouble?
We knew this would happen and it is why we didn't want to make our GCC4
ABI officially stable. It means we can make the switch and drop gcc4
support at some point.
Why not switch to clang and its libc++, and standardize on its ABI?
I believe clang’s libc++ is expected to remain binary compatible over the
long term, not just across minor revisions.
gcc4 was released in 2007, so they kept the ABI stable for 9 years. That
already is quite "long term".
gcc5 introduces ABI versionning so the gcc4 ABI is still supported in
it.
As to the why not: no one has submitted a patch to get Haiku to build
and run as a gcc2/clang hybrid using the old glibc/libstdc++ for the gcc2 side,
and a modern libc/libc++ for the clang side (I don't think getting
libc++ to run on our ancient libc is reasonable).
If someone is willing to make the effort, and there are actual benefits
in making the switch, we could change our mind again as to which
compilers we ship.
--
Adrien.
Other related posts:
