Mapping Python to LLVM
blog.exaloop.io
Mapping Python to LLVM
1–10 of 34 posts
Re: Mapping Python to LLVM
#2Makes me very suspect about the rest of this project when they try to glide past all of these issues with nary a mention.
Re: Mapping Python to LLVM
#3You can be efficient without sacrificing correctness; using LLVM shouldn’t mean “throw out arbitrary-precision semantics”.
Re: Mapping Python to LLVM
#4> int can become an LLVM i64 You can be efficient without sacrificing correctness; using LLVM shouldn’t mean “throw out arbitrary-precision semantics”.
Re: Mapping Python to LLVM
#5Don’t think of it as a Python compiler, it is its own language. (Esp. re choice of int == i64, this saves SO MUCH computation for the CPU.)
I will say though that I’m not sure where to use it yet, since it’s too immature for important projects and also aims at the “we need a nuclear bomb” level performance.
Re: Mapping Python to LLVM
#6Re: Mapping Python to LLVM
#7Re: Mapping Python to LLVM
#8If I recall it really wasn't that much faster than CPython given the overhead, but it's been a long time; if it was faster I assume it wouldn't have been abandoned.
Re: Mapping Python to LLVM
#9Re: Mapping Python to LLVM
#10How does Codon leverage the lessons learned from Unladen Swallow?