about summary refs log tree commit diff
path: root/src/test/codegen/gdb_debug_script_load.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2018-01-17 09:22:22 +0000
committerbors <bors@rust-lang.org>2018-01-17 09:22:22 +0000
commit3e49ada7528bf664b2ccc8516a9ef7d21849a70b (patch)
treea4795cd8c82d743c3241066798bc2ee9bfe031c3 /src/test/codegen/gdb_debug_script_load.rs
parentda569fa9ddf8369a9809184d43c600dc06bd4b4d (diff)
parent8c09d29d04dabc96a3ae88d914e3b54220952943 (diff)
downloadrust-3e49ada7528bf664b2ccc8516a9ef7d21849a70b.tar.gz
rust-3e49ada7528bf664b2ccc8516a9ef7d21849a70b.zip
Auto merge of #47035 - acfoltzer:dep-info-tweak, r=alexcrichton
Remove dep-info files as targets in themselves

If you ask `rustc` to `--emit dep-info`, the resulting dependency file contains a rule for producing the dependency file itself. This differs from the output of `gcc -MD` or `clang -MD`, which only includes dependency rules for the object files produced.

Tools like Ninja often consume and delete dependency files as soon as they’re produced for performance reasons, particularly on Windows. In the case of `rustc` output, though, the recently-deleted dependency file is cached by Ninja as a target, and therefore triggers a rebuild every time.

This very small patch removes the dep-info file from the list of output filenames, so it matches the behavior of gcc and clang.
Diffstat (limited to 'src/test/codegen/gdb_debug_script_load.rs')
0 files changed, 0 insertions, 0 deletions