Yeah, that would do it, but unfortunately doesn't apply in my situation (I need the function in question to be multi-threaded). I have done a bit of gcc backend work, but it's been a while. If you could tell me exactly what to download and what patches to apply to get the right source tree, I'll take a look at it when I get a moment.
Did you see my other message about the jmp instruction? I imagine that's deeper vodoo than the call thing, but I could be wrong. Thanks, Frank On Thu, Dec 23, 2004 at 10:28:20PM +0100, Heiko Panther wrote: > > >Any update on this? I've worked around it (painfully) for now, but would > >like > >to see a fix. If someone could point me in the right direction I could > >take a > >look at it myself, but don't really have a lot of time to spend on this at > >the > >moment (trying to get product out the door). > > > > The not-so painful workaround for me was to declare the function pointer > static. When it's not automatic, it's not on the stack, and not addressed > register-indexed. > As for fixing it, for someone who's not familiar with the gcc backend > (machine definition and that stuff) it's probably quite a bit of learning > first. My shallow knowledge of it made me change my mind about trying to > fix it after half an hour. > > Heiko > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
