Re:PyPy is faster than C, again: string formatting
by ori_b on Tuesday August 02, 2011 @04:46PM
(#2838638)
GCC got that option recently with '-flto' (or whatever it was to enable link time optimization)
Re:PyPy is faster than C, again: string formatting
by sausagefeet on Tuesday August 02, 2011 @06:40PM
(#2838995)
Is anyone working on a JIT for object code? I'm thinking we could keep all our SO's how they are now since they are great for updating versions of libraries with bugs, but have a JIT that takes care of profiling and inlining functions from other modules.
Re:PyPy is faster than C, again: string formatting
by fanf2 on Wednesday August 03, 2011 @07:02AM
(#2840599)
LLVM is designed to be able to do this.
Re:PyPy is faster than C, again: string formatting
by scott_s on Tuesday August 02, 2011 @04:14PM
(#2838524)
See my reply below. I'm fully aware of the relationship C has to systems programming.
Re:PyPy is faster than C, again: string formatting
by cube13 on Tuesday August 02, 2011 @04:14PM
(#2838526)
Depends on their GCC options. If it's the default option, it should be using the shared library. If they changed it to statically link libc, that should produce a(possibly considerable) performance boost.
I'm not a GCC expert, but Microsoft C compilers could inline cross-module code since the beginning of time. His example may actually produce different results under msvc with /GL flag and with static linking enabled.
"...Inline a function in a module even when the function is defined in another module..." http://msdn.microsoft.com/en-us/library/0zza0de8%28v=vs.80%2...