Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle LTO with an rlib/cdylib crate type #8254

Merged
merged 1 commit into from
May 18, 2020
Merged

Handle LTO with an rlib/cdylib crate type #8254

merged 1 commit into from
May 18, 2020

Commits on May 18, 2020

  1. Handle LTO with an rlib/cdylib crate type 

    In the case that LTO is happening but we're also generating a
cdylib/rlib simultatneously that means that the final artifact will use
the rlib but the cdylib still needs to be produced. To get this to work
the cdylib's dependency tree needs to be compiled with embedded bitcode.
The cdylib itself will be linked with the linker because we can't LTO an
rlib+cdylib compilation, but the final executable will need to load
bitcode from all its deps.

This is meant to address rust-lang/rust#72268
    @alexcrichton
    alexcrichton committed May 18, 2020
    Configuration menu
    Copy the full SHA
    b45fd8f View commit details
    Browse the repository at this point in the history