This question is due to a 68k based Texas Instruments calculator program that I am trying to adapt to run on environments that are more familiar to me.

The main problem I'm having is that it mixes 68k assembly into the C source file. While I'm confident enough to remove various TI system calls, the dependency on a 68k target has prevented me from being able to recompile my attempted modifications.

Alternately, can vbcc handle mixed 68k assembly and C? If so, it doesn't seem to like the gcc method of doing this.

This is the simplest example of a mixed source function from the program:

Code:
Clipboard01.jpg

btw Why does the forum Code feature clobber indentation and backslashes?

MorphOS SDK does not contain a 68k target compiler. It won't compile any 68k asm.

Quote:
Inline asm is always processor dependent. You have to protect such code with appropriate checks.

Quote:
Yes, your snippet is GCC-style inline asm. VBCC uses a different approach.

You can compile 68k assembly to object code and include this code as binary blob in your PPC native build. Or even in 68k native build if you want to. I did that to Scout and FileMaster long ago and I just called 68k code from PPC code using the built-in 68k emulator.

However, inline asm is different case and in this case it would be better replace inline asm with native code. You find some useful macros from hardware/byteswap.h header file.

So try to replace inline asm with native code. Perhaps use macros to conditionally use 68k inline asm or native code or MorphOS macros that do the same.