From 14bff5fb703c48d00cc6017be73d854716c5b37a Mon Sep 17 00:00:00 2001 From: Aland <158173939+aland-omed@users.noreply.github.com> Date: Wed, 22 Jul 2026 02:13:52 +0300 Subject: [PATCH] docs: Update profiling inlining guidance --- src/profiling.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/profiling.md b/src/profiling.md index 66eabe7d8c..fd0592b11f 100644 --- a/src/profiling.md +++ b/src/profiling.md @@ -109,6 +109,6 @@ The llvm-lines output is affected by several options. MIR optimizations have little impact. Compared to the default `RUSTFLAGS="-Z mir-opt-level=1"`, level 0 adds 0.3GB and level 2 removes 0.2GB. -As of July 2022, -inlining happens in LLVM and GCC codegen backends, -missing only in the Cranelift one. +As of July 2026, Cranelift sysroot builds explicitly enable +MIR inlining with `-Zinline-mir`, while the LLVM and GCC codegen backends may +also perform inlining during code generation.