Looks to me, "C from C" on Windows got optimized away

I don't think so. (Could be wrong but.)
A clearer ilustration is (hopefully) this script:

use Time::HiRes qw(time);

use Inline C => Config =>
  #OPTIMIZE => '-O0',
  FORCE_BUILD => 1;

use Inline C => <<'EOC';

void foo() {}

void foo_bar(int x) {
  int i;
  for(i = 0; i < x; i++){
    foo();
  }
}


EOC

$iterations = 10000000;
$t = time;
foo() for 1 .. $iterations;
print "# ", time - $t, "\n";

$t = time;
foo_bar($iterations);
print "# ", time - $t, "\n";
[download]

As it stands, with optimization enabled, it outputs (on Windows):

# 1.02960205078125
# 1.00135803222656e-005
[download]

Now that second value does look like something was optimized away. I'm thinking the loop is simply doing nothing at each iteration.
When we switch optimization off by including the "OPTIMIZE => '-O0'" line, the output changes to (on Windows):

# 1.10760188102722
# 0.0196361541748047
[download]

The "C from C" code now takes 500 times longer to execute - because, I think, this time foo() is actually being called at each iteration. But it's still 50 times quicker than calling "C from Perl".

I've no useful ideas regarding things that can be done to enable Windows to access C subs as quickly as it can access Perl subs - and that's the main reason that I'm avoiding that aspect.

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.