If you're using Clang/LLVM you can also enable ML inlining[1] (assuming you build from source) which can save up to around 7% if all goes well. There are also

If you're using Clang/LLVM you can also enable ML inlining[1] (assuming you build from source) which can save up to around 7% if all goes well. There are also talks of work on just brute forcing the inlining for size problem for embedded releases for smallish applications. It's definitely feasible if the problem is important enough to you to throw some compute at it [2]. 1. https://github.com/google/ml-compiler-opt https://github.com/google/ml-compiler-opt 2. https://doi.org/10.1145/3503222.3507744 https://doi.org/10.1145/3503222.3507744