Yokemate of Keyboards
Posts: 11631 from 2003/5/22
>>> Change to cpu working in 32 bit low endian mode made API not compatible with
>>> old 68k amiga software.
>> What does API have to do with endianness here?
> CPU change to one not working in 32 bit big endian mode, twist API about 180 degrees
No, the API has not been twisted.
> and made not compatible with old 68k apps.
No, it's not the AROS API that is incompatible with m68k apps but the AROS/x86 ABI
. ABI and API are different things. You can google and read up on the difference between them. If you do this, you'll know why an API doesn't have anything to do with endianness, whereas an ABI has.
> cpu change to to one not working in 32 bit big endian mode, made API not
> compatible with old 68k apps.
You already said this and it's still false. And it will remain false no matter how often you will repeat it (not that this has stopped you in the past...).
> first thing to do after API change to compatible with old 68k apps
To make AROS/x86 compatible with m68k apps, the required ABI must be provided. On MorphOS and OS4 this is done by means of the integrated m68k emulation. On AROS/x86, this would indeed be problematic because of opposing endianness between host OS and guest binaries (Emumiga
failed for a reason).
> no binary compatibility with 68k apps