diff options
| author | bors <bors@rust-lang.org> | 2023-10-11 23:00:24 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-10-11 23:00:24 +0000 |
| commit | 9d1e4b7870f0aecb9f53e71f3cca3529b21d677a (patch) | |
| tree | 5fd72b734dec09d5e7c5091d8896d08d23a98486 /compiler/rustc_mir_transform/src/coverage/graph.rs | |
| parent | 475c71da0710fd1d40c046f9cee04b733b5b2b51 (diff) | |
| parent | 3f9ab7ad9258b812b42361c12f993489376995ee (diff) | |
| download | rust-9d1e4b7870f0aecb9f53e71f3cca3529b21d677a.tar.gz rust-9d1e4b7870f0aecb9f53e71f3cca3529b21d677a.zip | |
Auto merge of #116448 - Kobzol:bootstrap-host-flags, r=onur-ozkan,petrochenkov
Pass rustc shim flags using environment variable This PR implements a generalized way of passing of host flags to the `rustc` shim in bootstrap, as proposed [here](https://github.com/rust-lang/rust/pull/116278#discussion_r1346979960). I tried to implement the bootstrap side using `OsString`, but then I realized that the shim code was using `env::var` before anyway, instead of `env::var_os`, so I just settled on a `String`. The shim side is still general and uses `env::vars_os` now. I'm not sure if we actually need to do something with the `rustdoc` shim. It *seems* to me that the env. vars passed to it (`RUSTDOC_LINKER`) and (`RUSTDOC_LLD_NO_THREADS`) could just be passed to cargo directly (or rather, the commands that they invoke in the shim could be passed directly). I'm not sure why are they set by the shim. r? `@onur-ozkan` CC `@petrochenkov`
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/graph.rs')
0 files changed, 0 insertions, 0 deletions