🚀 go-pugleaf

MW Ron wrote:
> 
> In article <3D19F129.B549F3E0@arc-software.com>,
>  Paul Russell <prussell@arc-software.com> wrote:
> 
> >I'm trying to integrate a chunk of gcc PowerPC assembler code into a CW
> >8 Mach-O project. I've tried two approaches, neither of which seem to
> >work. Has anyone else had more success than I have ?
> >
> >(i) fix the syntax (by hand !) and put the code into an inline asm {}
> >function - this fails because CW complains that there aren't enough free
> >registers (despite teh fact that I'm only using about 12 GPR's)
> >
> >(ii) assemble with gcc and try to link in the object file - the Mach-O
> >Importer barfs with an error about an unsupported relocation type or
> >some such
> >
> >Surely it shouldn't be this hard to link is some very straightforward
> >asm functions, that already work with gcc ?
> 
> What linker are you using? the Apple GCC linker or Metrowerks Mach-O
> linker,  do you have a small example project (or code for a stationery
> project) that you can send that I can forward on.
> 

I'm using the default MetroWerks "Mac OS X PowerPC Mach-O" linker, and
the default file mappings, which map object files to "Mach-O Importer",
which seems to be where the error message is coming from. I think I
tried changing the linker but it didn't make any difference.

If I make a small asm function that does nothing then I can link that in
OK - the problem seems to occur when the function has branches in it -
the Mach-O Importer doesn't like something about the relocation info in
the object file. Since these would be relative branches I can't imagine
what the problem would be.

As you suggest, I'll put together a demo which illustrates the problem.

Paul