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',
[download]

(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

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.