Hard to say. When I should guess, I would say that your WarpOS-compiler still calls the 68k assembler? Or the compiler frontend expects a different assembler version?
Probably an installation problem. Try to find out with SnoopDos which binaries are really started. Maybe you get a clue from that.
My personal opinion is that you should look out for a real WarpOS compiler. Most of those gcc ports I have seen do neither support the WarpOS PowerOpen ABI nor do they create EHF object files.
Instead they will still generate ELF objects using the V.4-ABI. And to make that work they need a wrapper function for each WarpOS kernel call to fix the stack frame. But this doesn't help for callback functions, of course. So it might happen that your stack gets corrupted...
|