News for hackers. Stuff that matters.
Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by sanxiyn on Thursday April 03, 2014 @02:28PM (#7524947)
Those who do not learn history are doomed to repeat it.

http://qinsb.blogspot.kr/2011/03/unladen-swallow-retrospecti...

Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by dbecker on Thursday April 03, 2014 @03:54PM (#7525894)
Those who do not learn history are doomed to repeat it.

I'd bet the Dropbox team is aware of unladen swallow and the issues it faced.

Applied too broadly, that quote would mean "never try anything where others have failed."

Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by kmod on Thursday April 03, 2014 @02:37PM (#7525025)
I can't speak to the non-technical reasons mentioned in the post, but there's good reason to believe that LLVM is in a very different state than the time that Reid wrote this, particularly wrt JIT support: the JIT engine has been completely replaced. Both of the things that he mentions (lack of back-patching, lack of gdb support) have been added to LLVM mainline.
Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by sanxiyn on Thursday April 03, 2014 @02:50PM (#7525109)
LLVM's JIT support has changed a lot, but one thing didn't change: "LLVM code generation and optimization is good but expensive."

Even LLVM's "fast" code generator is slower than most JITs' code generators.

Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by kmod on Thursday April 03, 2014 @03:01PM (#7525186)
Definitely true; there are some overheads that could be low-hanging fruit to optimize, but the real solution is most likely to use a tiered-compilation system. ie only invoke the full LLVM code generator once a function has been called 10,000 times. It's definitely an open question as to how to get faster compilation times out of it; we have a simple LLVM interpreter but since LLVM isn't designed for interpretation it's pretty slow.

I think you can look at the people who are interested in adding LLVM tiers to their JITs (ex Apple, Facebook) to see that we're not the only ones that think there can be a place for "good but expensive" code generation in a JIT.

Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by jbs3982 on Thursday April 03, 2014 @09:09PM (#7528426)
Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by perone on Thursday April 03, 2014 @02:54PM (#7525137)
From Dropbox to the python-dev mailing list:

"(...). As for Unladen Swallow, there are some reasons to think that LLVM has matured greatly in the past few years, particularly in the JIT engine which has been completely replaced. I'm not sure if that's the only part to the story; I'd be interested in talking with any of the people who were involved or knowledgeable about the project."

Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by ahomescu1 on Thursday April 03, 2014 @02:33PM (#7524988)
It's my impression that Unladen Swallow failed because of insufficient manpower, not because of the general approach. It's true that LLVM is missing some features for a JIT like this (mainly OSR and back-patching), but those can be added. For example, there was a discussion a few months ago on llvm-dev about adding patching support [1] (it was originally meant for garbage collectors, but would also work for JITs).

1 - http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-October/0665...

Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by driax on Thursday April 03, 2014 @02:38PM (#7525038)
It is my impression that LLVM has matured quit a bit since unladen swallow. Not least in the JIT domain. A lot of unladen swallows development was spent on improving LLVM and not on implementing Python as fast a possible. I seem to recall that the LLVM developers have had discussions on how to better support JIT compilers in LLVM, since unladen swallow, some of it precisely because unladen swallow failed.
Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by krishna2 on Thursday April 03, 2014 @08:45PM (#7528343)
Guido works at Dropbox. I am sure he is advising - and I bet, he has seen pretty much all the previous attempts closely to let them make any obvious mistakes.
Re:Announcing Pyston: an upcoming, JIT-based Python implemen... by masklinn on Friday April 04, 2014 @11:46AM (#7532144)
> Guido works at Dropbox. I am sure he is advising

Guido worked at Google during Unladen Swallow, he was not involved. From the comments of Pyston's announcements, here's the extent of GvR's involvement:

> Guido's advice has been extremely helpful, but so far we haven't been able to get any code from him :/