about summary refs log tree commit diff
path: root/compiler/rustc_mir/src/transform/coverage/graph.rs
diff options
context:
space:
mode:
authorDylan DPC <dylan.dpc@gmail.com>2021-02-18 16:57:43 +0100
committerGitHub <noreply@github.com>2021-02-18 16:57:43 +0100
commitefdcb4301be26f96ee6e2df18f7b47dcfe89b129 (patch)
tree55327092c7e615916a77097f6e9bcda60b139266 /compiler/rustc_mir/src/transform/coverage/graph.rs
parent555db2da70fb10103263148d678a72901a455d50 (diff)
parent6165d1cc72f8af55b3ef16ad81273b80876f9518 (diff)
downloadrust-efdcb4301be26f96ee6e2df18f7b47dcfe89b129.tar.gz
rust-efdcb4301be26f96ee6e2df18f7b47dcfe89b129.zip
Rollup merge of #82256 - eddyb:time-passes-stderr, r=varkor
Print -Ztime-passes (and misc stats/logs) on stderr, not stdout.

I've tried not to change anything that looked similar to `rustc --print`, where people might use automation, and/or any "bulk" prints, such as dumping an entire Graphviz (`dot`) graph on stdout.

The reason I want `-Ztime-passes` to be on stderr like debug logging is I can get a complete (and correctly interleaved) view just by looking at stderr, which is merely a convenience when running `rustc`/Cargo directly, but even more important when it's nested in a build script, as Cargo will split the build script output into stdout (named `output`) and `stderr`.
Diffstat (limited to 'compiler/rustc_mir/src/transform/coverage/graph.rs')
0 files changed, 0 insertions, 0 deletions