@wawa

errm, at least as i understand it. i dont have enough interest for it thugh. admittedly.

@wawa

Quote:

it does as certainly any/most aros software for the same architecture. arix is something like highly integrated aros hosted with an invisible host.

It's not the arix you know from Jasons github repository. That one was an intermediate step between regular AROS hosted and something more tightly bound to the linux. What I'm working on right now is something completely different.

It may look the same, just like here:
Quote:

PutMsg(arixPort, &msg); WaitPort(reply);

but if you look more carefully, you will notice differences, like mixed calls to arix libraries, linux syscalls or glibc:

Quote:

printf("doing %d iterations\n", NUM_ITER); clock_gettime(CLOCK_REALTIME, &t0); for (i=0; i < NUM_ITER; i++) { PutMsg(arixPort, &msg); WaitPort(reply); DiscardMsg(GetMsg(reply)); }

Finally, if you look at the whole you will notice that the messages are passed by value through an unix socket, not by reference as on AmigaOS, as they are crossing a boundary between two linux processes. Even more strange, the arixPort is not a pointer to a struct MsgPort because it cannot be (the MsgPort was created in another process). Instead, there is:
Quote:

uuid_t arixPort = MAKE_UUID(0x00000001, 0x0000, 0x4000, 0x8000 | NT_MSGPORT, 0x000000000000);

To some degree it is source code compatible, but only where possible. Where not, I do not hesitate to redesign API and break compatibility totally.