[haiku-development] Re: ptrdiff_t and size_t in Haiku/GCC
- From: Zenja Solaja <solaja@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 26 Jun 2009 08:05:30 +1000
I think long ago it was made public knowledge that Haiku R1 promises to
maintain binary compatibility only for the 32 bit GCC 2.9x version. A lot
of the key developers stressed that any code made with the GCC 4.x compiler
will probably not work with Haiku R2, since the API will definately change
(for a number of reasons, which also includes a 64 bit API). Given the
drama of breaking API compatibility, the consensus at the time seemed to be
that Haiku will only officially break binary compatibility once (in the near
future) and that would be with R2 (but older programs made for R1 will still
run). Hence application developers have 2 known official platforms:
1) Haiku R1, which is 32 bit gcc2.9x, and Haiku R1 API.
2) Haiku R2, which is gcc4.x, maybe 64 bit, maybe different object format,
and definately new R2 API. Unknown if R1 programs would even be 100% source
compatible, since API will change.
Anything in between (like Gcc 4.x, 64-bit port, new API) is not guaranteed
to be binary compatible with official R2. I was under the impression that
the current GCC 4.x version of R1 was from day #1 claimed to be only an
interim solution, with no binary backwards compatibility guaranteed.
Cheers.
Zenja
2009/6/26 André Braga <meianoite@xxxxxxxxx>
> Em 25/06/2009, às 15:38, "Ingo Weinhold" <ingo_weinhold@xxxxxx> escreveu:
>
>> works for both 32 and 64 bit architectures
>>
>
> Which reminds me of asking: are there plans to make Haiku64 able to run
> unmodified Haiku32 binaries? I'd believe there would be no compiler issues,
> as other OSs have managed to pull it off, even Windows --and boy are there
> some arcane compilers for that thing--, but what do I know.
>
>
> Cheers,
> A.
>
Other related posts:
