> Couldn't you just answer the question?

That would mean simply quoting what Neko wrote anyway. And if you hadn't ignored my answer from 5 months ago it would have been one step less now ;-)

> I think you mean running code in big-endian mode.

Yes, that's what it's all about when we're talking about running m68k code transparently, which is what Jim and I did here.

> The only time I think code ordering would make a difference is when you
> want to emulate something (e.g. 68K or PPC)

Err, that's exactly what this discussion has been about, i.e. running existing m68k code transparently on MorphOS/ARM the same way existing m68k code is transparently running on MorphOS/PPC right now.

> the emulator would handle that transparently

I doubt that's possible within a singular address space OS that is based on message passing concept like AmigaOS or MorphOS' ABox. There could be a way around this, though:

http://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=7771&forum=3&start=15

But that's an idea laire doesn't seem to like too much:

"Either you run everything as big endian with some x86 68k emulation and allow "native" code with some butt ugly compiler byte reordering thowing performance away. Some may argue that this might still be faster than existing ppc systems and this might be even true but there are things which are so ugly you just don't do them."
http://moobunny.dreamhosters.com/cgi/mbmessage.pl/amiga/126048.shtml