Skip to content

--emit KIND=PATH affects crate hash vs --emit KIND #86044

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
Closed
jsgf opened this issue Jun 5, 2021 · 1 comment
Closed

--emit KIND=PATH affects crate hash vs --emit KIND #86044

jsgf opened this issue Jun 5, 2021 · 1 comment
Labels
C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@jsgf
Copy link
Contributor

jsgf commented Jun 5, 2021

When emitting to a specific path with --emit KIND=PATH the crate hash is affected by what PATH is.
If you use --emit KIND -o PATH, or --out-dir PATH the crate hash is unaffected.

Meta

rustc --version --verbose:

rustc 1.54.0-dev
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.54.0-dev
LLVM version: 12.0.1
@jsgf jsgf added the C-bug Category: This is a bug. label Jun 5, 2021
@jsgf jsgf mentioned this issue Jun 6, 2021
Closed
jsgf added a commit to jsgf/rust that referenced this issue Jun 10, 2021
@jsgf
In --emit KIND=PATH options, only hash KIND
c14790f 
The PATH has no material effect on the emitted artifact, and setting
the patch via `-o` or `--out-dir` does not affect the hash.

Closes rust-lang#86044
@inquisitivecrystal
Copy link
Contributor

@rustbot label +T-compiler

@rustbot rustbot added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Jun 20, 2021
@bors bors closed this as completed in a26d99f Jun 22, 2021
@jsgf jsgf mentioned this issue Jul 14, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jsgf @inquisitivecrystal @rustbot