in reply to Re^8: Inline::C on Windows: how to improve performance of compiled code?
in thread Inline::C on Windows: how to improve performance of compiled code?

Both renditions of foo() do essentially the same thing. But the rendition that has been commented out won't work when PERL_NO_GET_CONTEXT is defined, whereas the other rendition will.

But all that does is move the mapping from int to SV from explicit to implicit. Ie. moves the mapping from the C function to the IC wrapper code.

And 95% of the overhead is (already) in the wrapper code.

Maybe the benefits of PERL_NO_GET_CONTEXT are confined to gcc/mingw, but I have just tried it in two different pieces of code (and previously when it came up also) and it never seems to make a jot of difference.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". The enemy of (IT) success is complexity.
In the absence of evidence, opinion is indistinguishable from prejudice. Suck that fhit
  • Comment on Re^9: Inline::C on Windows: how to improve performance of compiled code?

In Section Seekers of Perl Wisdom