You may have seen https://www.phoronix.com/news/GCC-14-Haiku-OS-Support ;
(https://www.phoronix.com/news/GCC-14-Haiku-OS-Support).
Haiku support has *not* been merged in upstream GCC. (though it definitely
sounds
like it was from that commit message lol)
Here's the commit in question:
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=ead5103cc6f526bcc5a30c8c7185e9dd5de73d55
(https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=ead5103cc6f526bcc5a30c8c7185e9dd5de73d55)
It seems to be some reformation of this:
(which was merged into binutils to upstream Haiku support there)
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=d85e70a35bffa755fd3e9f4ccc6bf6c64953e85d
(https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=d85e70a35bffa755fd3e9f4ccc6bf6c64953e85d)
So, tldr; that gcc commit does not actually upstream all of our GCC code.
I submitted a full GCC patch back in 2018, however they asked for more unit
tests and some
contributor agreements to be signed:
https://gcc.gnu.org/legacy-ml/gcc-patches/2018-07/msg00874.html ;
(https://gcc.gnu.org/legacy-ml/gcc-patches/2018-07/msg00874.html)
It is *definitely* our goal to get Haiku's GCC toolchain upstream, and that
commit does indeed nudge us
a little in that direction... however it's a small portion of a larger commit
adding architecture support.
I've emailed a similar correction to Phoronix.
Thanks!
-- Alex
