Defining PERL_NO_GET_CONTEXT doesn't stop it from running, but it doesn't improve performance one iota
But you've defined PERL_NO_GET_CONTEXT too late for it to have any effect.
It needs to be done
prior to the inclusion of the 3 perl headers (EXTERN.h, perl.h and XSUB.h).
Hence, it needs to be done in the Inline::C Config section as
PRE_HEAD => '#define PERL_NO_GET_CONTEXT 1',
(The specified string, followed by a newline, will then be inserted in the generated XS file above the inclusion of those 3 headers.)
UPDATE:
I think you would be better off looking at ways to try and move some or all of your loop into C, rather than trying to optimise the calls from Perl to C
I totally agree with that. I think that's where the most significant savings will be found.
Cheers,
Rob
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.