Skip to content

xLTO: Code from standard library does not partake in linker-based LTO (unless compiling with -Clto) #64124

Open
@michaelwoerister

Description

@michaelwoerister

xLTO works by emitting LLVM bitcode instead of machine code and then letting the linker run LLVM optimizations (at a point where also code from C/C++ is available for IPO). In the current setup, this means that code from the standard library does not partake in the final LTO step because it is pre-compiled to machine code.

This limitation can be lifted by compiling to a staticlib with -Clto because the fat LTO step that rustc does pulls in the compressed bitcode version of the standard library and then emits the unified bitcode file for further processing by the linker. However, this adds an additional fat LTO step into the compilation pipeline, which is very costly.

In theory it should be possible to make rustc emit libstd LLVM bitcode into the staticlib instead of the object files (if -Clinker-plugin-lto is specified). The bitcode is available and rustc knows how to decompress it. Then the linker could do its LTO step with the standard library included but without the additional cost.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.A-codegenArea: Code generationC-feature-requestCategory: A feature request, i.e: not implemented / a PR.I-compiletimeIssue: Problems and improvements with respect to compile times.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions