[haiku-development] Re: Switch to Clang or GCC 4.9?
- From: Simon Taylor <simontaylor1@xxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 24 Apr 2014 09:24:50 +0100
On 23 Apr 2014, at 21:03, Jonathan Schleifer <js-haiku-development@xxxxxxxxxxx>
wrote:
> The problem is that it currently uses gcc as assembler and linker. In order
> to solve this, a Haiku class needs to be added to Clang, which I plan to do
> once I find the time.
Sounds like maintaining a Haiku copy of the clang source (or source tarball +
patch) will help to get this going then, without waiting for it to be
upstreamed.
> We'd still need libstdc++, which is part of GCC, though. Switching over the
> system to Clang is the first step, though. I think we can learn from FreeBSD
> here. Switching to libc++ would mean binaries are incompatible though. So we
> should decide whether we want Clang or GCC before R1, so that we don't have 3
> ABIs for R1 ;).
At least on OSX it is possible to link against either libstc++ or libc++. Do
they treat that as a separate ABI? I think it’s possible to mix and match code
that uses different standard libraries internally, as long as they don’t expose
them through public interfaces (ie std::vector<int> getVector() functions)?
Happy to be corrected on that point though.
Simon
Other related posts:
