comment on

Okay. I got I::C to work, and these are the results I get from running your (unmodified) benchmark here:

C:\test>792136.pl
Benchmark: timing 1 iterations of list, ref...
      list:  0 wallclock secs ( 0.05 usr +  0.00 sys =  0.05 CPU) @ 21
+.28/s (n=1)
            (warning: too few iterations for a reliable count)
       ref:  0 wallclock secs ( 0.03 usr +  0.00 sys =  0.03 CPU) @ 32
+.26/s (n=1)
            (warning: too few iterations for a reliable count)
2000001000000
2000001000000

C:\test>792136.pl
Benchmark: timing 1 iterations of list, ref...
      list:  0 wallclock secs ( 0.05 usr +  0.00 sys =  0.05 CPU) @ 21
+.28/s (n=1)
            (warning: too few iterations for a reliable count)
       ref:  0 wallclock secs ( 0.03 usr +  0.00 sys =  0.03 CPU) @ 31
+.25/s (n=1)
            (warning: too few iterations for a reliable count)
2000001000000
2000001000000

C:\test>792136.pl
Benchmark: timing 1 iterations of list, ref...
      list:  0 wallclock secs ( 0.05 usr +  0.00 sys =  0.05 CPU) @ 21
+.28/s (n=1)
            (warning: too few iterations for a reliable count)
       ref:  0 wallclock secs ( 0.03 usr +  0.00 sys =  0.03 CPU) @ 31
+.25/s (n=1)
            (warning: too few iterations for a reliable count)
2000001000000
2000001000000
[download]

Which is consistant enough to confirm my intuition. I'm not sure why you are getting different results--but I urge you to look closely at them.

BTW: Can you tell me where PERL_BITFIELD16 is typedef'd on your setup, because it was entirely missing as far as I can see on mine. Once I added:

#define OPCODE U16

#ifdef PERL_MAD
#  define MADPROP_IN_BASEOP    MADPROP*    op_madprop;
#else
#  define MADPROP_IN_BASEOP
#endif

typedef unsigned int PERL_BITFIELD16; /// <<< I added this!
typedef PERL_BITFIELD16 Optype;
[download]

I::C started working again?

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".

In the absence of evidence, opinion is indistinguishable from prejudice.

RIP PCW It is as I've been saying!(Audio until 20090817)

In reply to Re^5: profiling XS routines by BrowserUk
in thread profiling XS routines by jpl

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.