i hope for hints of what could be changed

The first hint that comes to mind is to perform the 1e8 function calls to foo() from inside C space, rather than from Perl space.
On top of the significant reduction in overhead, one then might also get to take advantage of C optimizations that are lost when the C function is called from Perl.
The following script aims at demonstrating the sort of savings you might get. I've changed foo() to be a little bit more than a no-op, in the hopes that it will remove the effect of clever C optimizations. (I don't know if I've been successful.): 
use Time::HiRes qw(time);

use Inline C => <<'EOC';

int foo(int x) {return x + 1;}

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

EOC

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

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

# Outputs (on Windows):
# 1.57560181617737
# 0.0026400089263916

[download]
On my Ubuntu (16.04) box, running perl-5.26, the same script outputs: 
# 1.80176305770874
# 0.0337138175964355

[download]
Cheers,
Rob

In reply to Re: Inline::C on Windows: how to improve performance of compiled code? by syphilis
in thread Inline::C on Windows: how to improve performance of compiled code? by vr

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.