s = (s >> 1) ^ (-(s & 1) & 0xd0000001);
I also timed it the way you asked, with wall clock time over 100M iterations (10M runs too fast to time). Surprising even me, getpid wins by almost a full second.Got another challenge for me to write code for?
Want the punch line? OSX getpid averages under 100 cycles; snprintf (no IO) averages over 1000.
Breakpoint 1, 0x96210c44 in getpid ()
(gdb) disp/i $eip
2: x/i $eip 0x96210c44 <getpid>: call 0x96210c49 <getpid+5>
(gdb) stepi
0x96210c49 in getpid ()
2: x/i $eip 0x96210c49 <getpid+5>: pop %ecx
0x96210c4a in getpid ()
2: x/i $eip 0x96210c4a <getpid+6>: lea 0xa6427a3(%ecx),%ecx
0x96210c50 in getpid ()
2: x/i $eip 0x96210c50 <getpid+12>: mov (%ecx),%eax
0x96210c52 in getpid ()
2: x/i $eip 0x96210c52 <getpid+14>: test %eax,%eax
0x96210c54 in getpid ()
2: x/i $eip 0x96210c54 <getpid+16>: jle 0x96210c57 <getpid+19>
0x96210c57 in getpid () 2: x/i $eip 0x96210c57 <getpid+19>: mov $0x14,%eax
0x96210c5c in getpid ()
2: x/i $eip 0x96210c5c <getpid+24>: call 0x961e8cf4 <_sysenter_trap>
I'm sorry, but you seem to have a wildly inflated idea of the speed of system calls on modern OSs. The real world just doesn't work like that. This is my last post on this thread.