Dual boot (i.e. same hardware), Ubuntu 17.10, Win10, threaded Perl 5.26 both. However, it seems some (default) flags (compiler options?) are set wrong for Inline::C on Windows. Here's output of no-op example for both systems:

$ perl -MTime::HiRes=time -MInline=C,'void foo(){}' -wE'$t=time;foo()f
+or 1..1e8;say time-$t'
5.57836294174194
$ perl -MTime::HiRes=time -wE'$t=time;sub foo(){}foo()for 1..1e8;say t
+ime-$t'
5.003093957901

>perl -MTime::HiRes=time -MInline=C,"void foo(){}" -wE"$t=time;foo()fo
+r 1..1e8;say time-$t"
11.325471162796

>perl -MTime::HiRes=time -wE"$t=time;sub foo(){}foo()for 1..1e8;say ti
+me-$t"
5.04568600654602
[download]

The use of Inline::C for particular case, where I noticed that, is exactly for huge number of calls of very simple sub (but not no-op, of course). I understand sub calls in Perl are expensive, I'll live with that, but I don't understand the result above.

To counter "it's because Linux is better", the script was moved from very old 32-bit Windows machine, and I noticed (though can't provide any solid numbers right now), that benchmarks for pure-Perl parts showed perhaps 6-fold speed improvement, while the main part, in C, no more than 2-fold. Therefore I have a suspicion about sub-optimal Inline::C defaults there, and i hope for hints of what could be changed.