Python JIT thautwarm The “Restrain” 目录 CONTENTS Preview 和其他JIT的比较 实现原理 如何参与开发 1 Preview 并行计算: SIMD并行, true threading 避开解释器开销: for-loop 避免嵌套函数开销: native function pointer, inline “All Add 2” restrain_jit/test/test_functional.py “All Add 2” JIT version: 局部函数无开销 “All Add 2” JIT using SIMD: “All Add 2” Benchmark: “All Add 2” Benchmark: Method Time Pure Python 7.71 JIT 0.089 JIT + SIMD SIMD 0.098 2 和其他JIT的比较 我们知道有Numba, hope JIT, Graal Python, 但Restrain 是不同的。 我把Restrain的特性称为“CPython Compatible” Working With Existing And Prospective C-Extensions 兼容C extensions, 尽管不能优化, 但可以做到调用的开销尽可能接近CPython

解放Python的 表达力，性能和安全性 Thautwarm 目录 CONTENTS 语法和语义扩展 JIT 静态类型 语法和语义扩展 表达力的扩展， 可用性的保留，白来的午餐？ 演示一小部分: 模式匹配, Quick Lambda, Pipe运算 语言决定思维模型 GNU-APL C++ Haskell 说 到 质 数 � 人 们 想 到 什 么 � 语言决定思维模型 Just In Time The Restrain Python JIT 为什么编译器从字节码开始着手? 栈机(stack machine)语义的优化问题？ Julia后端和Cython后端的差别？ 栈机到基于寄存器(register based)的 语义，控制流分析，SSA 和 Φ 节点和 栈机语义消除。 Cython JIT 基础架构。 为什么编译器从字节码开始着手? 因为运行时一旦开始你是拿不到源代码的。 来谈后端的问题。 Julia Cython 常见性能提升 100x 1-10x 小函数JIT 比Python慢1000倍 比Python快50% 启动时间 10s以上, “JAOT” 没有，调编译器快 循环折叠 有 有 Debug现场？ 每次打log等待30s 瞬秒(ms级) JIT 后端问题 同时， 由于Julia端目前固有的问题，不支持动态链接编译的 Python(例如Anaconda

(/LIBRARY) IS THE COMPILER... (/LIBRARY) IS THE COMPILER... JUST-IN-TIME (JIT) IS COMPILATION AT THE POINT OF NEED JUST-IN-TIME (JIT) IS COMPILATION AT THE POINT OF NEED 3 . 2WHAT IS JITTING? WHAT IS JITTING (/LIBRARY) IS THE COMPILER... (/LIBRARY) IS THE COMPILER... JUST-IN-TIME (JIT) IS COMPILATION AT THE POINT OF NEED JUST-IN-TIME (JIT) IS COMPILATION AT THE POINT OF NEED IT'S LIKE THE APPLICATION (/LIBRARY) IS THE COMPILER... 3 . 2WHY JIT-COMPILE? WHY JIT-COMPILE? 3 . 3WHY JIT-COMPILE? WHY JIT-COMPILE? AOT IS NOT POSSIBLE AOT IS NOT POSSIBLE 3 . 3WHY JIT-COMPILE? WHY JIT-COMPILE? AOT IS NOT POSSIBLE

still today, are actually a continuum.Papers in this talk github.com/jfbastien/jit-talk CppCon Slack channel #sig_jit I’ll cover 20-some papers in this talk, and have collected them on a GitHub repo years. We’ve also got a CppCon Slack channel: SIG_JIT (Special Interest Group). In a way this talk isn’t my usual talk because it’s more of a lecture on JiT compilers, where I’ll outline the papers that spoke than usual, from these papers. First, some definitions.JiT JiT Just-in-Time compilation With some artistic liberty, folks usually think of JIT as: The executable code changes after the program is loaded

Profiler Bar example(Foo&) example+0 pushq example+2 pushq example+4 ...JIT Code jit+0 movabs jit+7 ... jit+n TRAP 1. Inject OI into the target process 2. Wait for a thread to hit our example+0 pushq example+2 pushq example+4 ... Data Buffer TRAP TRAPThread A JIT Code jit+0 movabs jit+7 ... jit+n TRAP 1. Inject OI into the target process 2. Wait for a thread to hit our example+0 pushq example+2 pushq example+4 ... Data Buffer TRAP TRAPThread A JIT Code jit+0 movabs jit+7 ... jit+n TRAP 1. Inject OI into the target process 2. Wait for a thread to hit our

COMPILER · JIT For PHP7 · Require Gcc 4.8 +(Global Register) · X86-32/64 Supported · Using Dynasm To Emitting Machine Codes(Mcode)[2] · Already Opened Source[3] BRAND NEW WAY Compiler JIT Type Inference opcache.jit=1 2 0 5 Use AVX JIT Strategy Register alloc JIT Level 0: JIT functions on load 1: JIT functions on execute 2: JIT most frequently called functions on first requrest 3: JIT functions functions after N calls or loop iterations 4: JIT functions with @jit annotation 0: JIT off 1: Minimal optimization 2: Basic optimization 3: optimize based on type-inference 4: optimize based on type-Inference

x86_64. The last number stands for the features: 0: No anti-debug, JIT, advanced mode features, high speed 7: Include anti-debug, JIT, advanced mode features, high security It’s possible to obfuscate --list pyarmor download --list windows pyarmor download --list windows.x86_64 pyarmor download --list JIT pyarmor download --list armv7 After pyarmor is upgraded, however these downloaded dynamic libraries Each feature has its own bit 1: Anti-Debug 2: JIT 4: ADV, advanced mode 8: SUPER, super mode For example, windows.x86_64.7 means anti-debug(1), JIT(2) and advanced mode(4) supported, windows.x86_64

x86_64. The last number stands for the features: 0: No anti-debug, JIT, advanced mode features, high speed 7: Include anti-debug, JIT, advanced mode features, high security It’s possible to obfuscate --list pyarmor download --list windows pyarmor download --list windows.x86_64 pyarmor download --list JIT pyarmor download --list armv7 After pyarmor is upgraded, however these downloaded dynamic libraries Each feature has its own bit 1: Anti-Debug 2: JIT 4: ADV, advanced mode 8: SUPER, super mode For example, windows.x86_64.7 means anti-debug(1), JIT(2) and advanced mode(4) supported, windows.x86_64

0: No anti-debug, JIT, advanced mode features, high speed 3.4. Distributing Obfuscated Scripts To Other Platform 13 PyArmor Documentation, Release 6.2.0 • 7: Include anti-debug, JIT, advanced mode features --list pyarmor download --list windows pyarmor download --list windows.x86_64 pyarmor download --list JIT pyarmor download --list armv7 After pyarmor is upgraded, however these downloaded dynamic libraries feature has its own bit • 1: Anti-Debug • 2: JIT • 4: ADV, advanced mode • 8: SUPER, super mode For example, windows.x86_64.7 means anti-debug(1), JIT(2) and advanced mode(4) supported, windows. x86_64

forwarding, encapsula�on, etc. An in-kernel verifier ensures that BPF programs are safe to run and a JIT compiler converts the bytecode to CPU architecture specific instruc�ons for na�ve execu�on efficiency linked, either choice is valid. CONFIG_BPF=y CONFIG_BPF_SYSCALL=y CONFIG_NET_CLS_BPF=y CONFIG_BPF_JIT=y CONFIG_NET_CLS_ACT=y CONFIG_NET_SCH_INGRESS=y CONFIG_CRYPTO_SHA1=y CONFIG_CRYPTO_USER_API_HASH=y through a compiler back end (e.g. LLVM), so that the kernel can later on map them through an in-kernel JIT compiler into na�ve opcodes for op�mal execu�on performance inside the kernel. The advantages for