A question about disabled LTO for Maturin itself

[zamazan4ik]

Hi!

As far as I understand, earlier the Maturin binary was optimized with LTO but since #1012 (comment) it was disabled due to a bug (if I am wrong here - please correct me).

Is it still an issue or we can re-enable LTO once again for Maturin? According to my local tests (the latest Maturin, Fedora 41, Rust 1.82), enabling lto = true for the Release profile at least reduces the binary size from 23 Mib to 19 Mib (didn't perform performance benchmarks though but I think the performance would be at least at the same level).

Thank you.

P.S. Please don't mess it up with the #1529 issue - here I am asking about enabling LTO for Maturin itself, not for the Rust-based Python packages built with Maturin.

[messense]

Enabled in release workflow for all targets except ppc64le: https://github.com/PyO3/maturin/actions/runs/12094076123/job/33725734878

error: failed to get bitcode from object file for LTO (could not find requested section)

error: could not compile `maturin` (bin "maturin") due to 1 previous error

[zamazan4ik]

Thank you for enabling LTO!

It's kinda interesting that LTO fails for the ppc64le target. I have made a quick research in the upstream and found similar issues:

• Build failure when using LTO with static linking rust-lang/rust#129888
• failed to get bitcode from object file for LTO (Bitcode section not found in object file) rust-lang/rust#94232

I will report your finding to the upstream to the issues above