Any idea what __restore_fpr_23 is?

I'm getting the following link errors when following the Codewarrior to
XCode conversion preparation. Anyone know what the story is here?

Link Error : undefined: '__restore_fpr_23' (code)
Referenced from 'Noise' in Noise.c

Link Error : undefined: '__save_fpr_23' (code)
Referenced from 'Noise' in Noise.c

Link Error : undefined: '__restore_fpr_21' (code)
Referenced from 'DNoise2' in Noise.c

Link Error : undefined: '__save_fpr_21' (code)
Referenced from 'DNoise2' in Noise.c

I've search the newsgroup for this and all I find are things to do with
link order which I've tried and to use the MSL library which I'm not
supposed to do.

"RogueWarrior" wrote in message

> I'm getting the following link errors when following the Codewarrior to
> XCode conversion preparation. Anyone know what the story is here?
>
> Link Error : undefined: '__restore_fpr_23' (code)
> Referenced from 'Noise' in Noise.c
>
> Link Error : undefined: '__save_fpr_23' (code)
> Referenced from 'Noise' in Noise.c
>
> Link Error : undefined: '__restore_fpr_21' (code)
> Referenced from 'DNoise2' in Noise.c
>
> Link Error : undefined: '__save_fpr_21' (code)
> Referenced from 'DNoise2' in Noise.c
>
> I've search the newsgroup for this and all I find are things to do with
> link order which I've tried and to use the MSL library which I'm not
> supposed to do.
>

IIRC, there were a bunch of those that saved and restored assorted registers
from the stack. I even remember seeing them: they're written in assembler
and buried somewhere in the MSL sources. I don't know if they're MW specific
or defined in some PPC ABI document and implemented by MW: they do fill a
need that any runtime library would have.

It would be interesting to know where they're being called. If the runtime
is using them internally they should be available. Is it possible that you
have some inline assembly that used them to manage stack frames, or a static
library compiled with CW?