4 ms·
Didn't see in the readme: why "final"? I could see it being considered complete or failed, but it's unclear.
by yjftsjthsd-h 10y ago
Didn't see in the readme: why "final"? I could see it being considered complete or failed, but it's unclear.
- connerbryan 10y agoI believe it's because llvmlite is now suggested. The llvmpy page mentions: > Warning > This project has been deprecated and is no longer being actively developed. We strongly suggest migrating to llvmlite. http://llvmlite.pydata.org/en/latest/ http://llvmlite.pydata.org/en/latest/
- jholman 10y agoWhy is this relevant? Are llvmpy and llvmcpy related?
- connerbryan 10y agoOh, my bad. You're right, I got my links mixed up. aleclm has responded with the correct answer, ignore mine.
- aleclm 10y agoFinal in the sense that hopefully we won't need a fourth one. It should provide the best performance (since the IR is not re-encoded in Python) and I've tried to make it flexible and future proof. llvmlite currently only supports LLVM 3.8, while I quickly tested llvmcpy with 3.4, 3.8 and 3.9 and works flawlessly. Still quite alpha, though.