Alex Crichton b45fd8ff0a 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
2020-05-18 08:48:52 -07:00
..
2019-11-24 18:42:45 -08:00
2020-05-05 14:34:09 -07:00
2019-11-24 18:42:45 -08:00
2019-11-24 18:42:45 -08:00
2020-02-17 19:03:57 -08:00
2019-11-24 18:42:45 -08:00
2019-11-24 18:42:45 -08:00
2019-11-24 18:42:45 -08:00
2019-12-03 10:47:32 -08:00
2019-11-24 18:42:45 -08:00
2020-02-19 16:46:29 -08:00
2020-05-01 01:16:30 +02:00
2019-11-24 18:42:45 -08:00
2020-05-14 15:56:01 -07:00
2019-12-23 12:00:22 +09:00
2019-12-29 20:42:50 +09:00
2020-01-31 12:05:14 -08:00
2020-01-13 13:27:33 -08:00
2020-04-01 14:31:06 -07:00
2019-11-24 18:42:45 -08:00
2019-11-24 18:42:45 -08:00
2020-04-01 14:31:06 -07:00
2019-11-24 18:42:45 -08:00
2019-11-24 18:42:45 -08:00
2019-11-24 18:42:45 -08:00
2019-11-24 18:42:45 -08:00
2020-03-15 15:16:36 -07:00
2019-12-17 17:44:37 -08:00