@matthey:
Quote:
|
There could be some instability issue which makes all AROS x86_64 software incompatible for example.
|
this is work in progress, there is only some test programs, fractyls running on multiple cores. the backwards compatibility is maintained, but one needs to keep an eye on it. lately snoopdos stopped workinng, i suspect some semaphore change in exec, fortunatelly there is aros native snoopy. but im of course concerned about such issues.
Quote:
Right. AROS can always have a 3rd ABI with every developer recompiling for every ABI and target CPU combination  .
|
given the code already compile for one platform of aros it will usually compile for another, 32 or 64 bit, smp or not.
of course things like pointers need to be defined to a proper type (IPTR if i recall right) which defaults to ULONG on 32bit archs. and on 68k you need to remember to use parametrizing macros and proper syntax for hooks, which will otherwise work on x86, even if wrong, but fail on 68k.
so 68k is actually least forgiving and proper reference platform.