Hi Jochen On Thursday 05 April 2007 16:08, Jochen Becher wrote: > Amithlon had such a feature of mixed binaries but I do not know how it > was implemented. I did read about this somewhere. I seem to rememeber that code starting at an odd address (68k code always has to start at even address) was assumed to be x86 code (and this would only work with x86 hosts, not anything else). I don't remember the details. Perhaps Martin Blom (the author of AHI might be of some help). He produced a version of GCC that produced "native" code for Amithon (little-endian x86, LOL). > Of course it would be possible to extend AmigaOS > similar to that what WarpUP did (having non-m68k code within Amiga Hunk > executables). One had to find a solution how to run x86 code that can be > scheduled for pre-emptive multitasking. And a way of giving function > parameters and results from m68k to x86 and vice versa. All in all that > is not a small project. This native library we used with AmigaXL was a > very simple approach without all those problems of generic mixed > binaries. Perhaps it might be useful to think about some specific problems you could solve and how they could be implemented. For instance, how might you create a version of icon.library (based on AROS code, perhaps) that ran on the host processor (decoding and displaying icons is dog slow, so could be a huge benefit). A generic way to run code on the host processor with mixed binaries (a la WarpOS or PowerUp) would make the job of creating native code easier, but the infrastructure required to do this much more complex. Cheers, Rich -- Richard Drummond Web: http://www.rcdrummond.net/ Mail: mailto:evilrich@xxxxxxxxxxxxxx