http://qs1969.pair.com?node_id=1216825


in reply to Inline::C on Windows: how to improve performance of compiled code?

So, have we by now established that a one-liner which does absolutely nothing in the loop, as I suggested, does not run in a time comparable to the one that uses the no-op inline function, but runs considerably faster?   That my hypothesis that this does not actually have to with the inline implementation but is endemic to the Perl interpreter version itself, has therefore now been tested and has been proven false?   I wasn’t clear if this idea had been tried or simply ignored and what the outcome turned out to be, if it was tried.

  • Comment on Re: Inline::C on Windows: how to improve performance of compiled code?

Replies are listed 'Best First'.
Re^2: Inline::C on Windows: how to improve performance of compiled code?
by syphilis (Archbishop) on Jun 18, 2018 at 00:07 UTC
    So, have we by now established that a one-liner which does absolutely nothing in the loop, as I suggested, does not run in a time comparable to the one that uses the no-op inline function, but runs considerably faster?

    I don't think we have, as it was never really the issue.
    The issue was more about some apparent additional overhead in calling XS subs on Windows, and what to do about it.

    I do, however, think it is very likely that code that does nothing 10 million times will execute significantly faster than code that calls a no-op 10 million times - and that your suggestion is most likely quite correct.

    Cheers,
    Rob
    A reply falls below the community's threshold of quality. You may see it by logging in.