News for hackers. Stuff that matters.
Re:PyPy faster than C (on a carefully crafted example) by burgerbrain on Friday February 04, 2011 @11:28AM (#2179975)
"I added a printf("%f\n",a) to the end of the file so the compiler wouldn't optimize the whole thing away. On my Cure 2 Duo 2.33Ghz, I got for gcc -O3:

1000000000.000000

real 0m4.396s user 0m4.386s sys 0m0.007s

and for gcc -O3 -flto -fwhole-program:

1000000000.000000

real 0m1.312s user 0m1.308s sys 0m0.003s"

Yet another case of somebody thinking they're making a clever comparison by forgetting to set their compiler flags properly.

Re:PyPy faster than C (on a carefully crafted example) by ehsanul on Friday February 04, 2011 @01:11PM (#2180429)
Please elaborate on what the correct flags would be, for those of use who wouldn't know.
Re:PyPy faster than C (on a carefully crafted example) by burgerbrain on Friday February 04, 2011 @09:07PM (#2182203)
Try reading the comment I just quoted.
Re:PyPy faster than C (on a carefully crafted example) by ehsanul on Friday February 04, 2011 @10:40PM (#2182376)
Oh, oops. Sorry, me and at least 3 others had a collective brain fart it seems. I had first thought you meant that both of those sets of compiler flags weren't quite right.
Re:PyPy faster than C (on a carefully crafted example) by bryanlarsen on Friday February 04, 2011 @02:44PM (#2180838)
Doesn't work if you're using a shared library, though.