6 ms·

There are two versions of Haiku, the hybrid 32-bit version uses the older GCC for compatibility with software written for BeOS, plus GCC 7.3.0 for modern app su

There are two versions of Haiku, the hybrid 32-bit version uses the older GCC for compatibility with software written for BeOS, plus GCC 7.3.0 for modern app support. The other is a 64-bit release with only the modern GCC and no backwards compatibility with BeOS apps. https://download.haiku-os.org/ https://download.haiku-os.org/

tcbawo 8y ago
What aspect of newer versions of GCC breaks the ABI? Are these things that can't be controlled?
- bebop 8y ago
  First, to add to the parent comment, you can install later versions of GCC on the x86 gcc2 builds as well. There is also a port of LLVM. Second, not directly related to what changed with the ABI, but it I think it would be more hassle than it is worth to try and make newer versions of GCC emit compatible binaries. There is work to run Haiku GCC 2.95 libraries alongside binaries built with a newer version. The runtime loader would be responsible for picking the correct so files. This also would work on the x64 builds as well, similar to how Linux (and others) can load x86 programs on x64 OS's. This feature is close to working but there were some last minute issues found, so it was left out of the Beta.
  - stuaxo 8y ago
    Ah, so BeOS programs could work under 64 bit haiku?
    - bebop 8y ago
      Yes, that is the plan if I understand correctly.
- amaranth 8y ago
  The GCC C++ ABI got a major overhaul in 3.4 so any C++ API won't be compatible. There may have been more platform-specific ABI changes too, I know mingw had one in the 4.x series.