Skip to content

Add documentation for RUSTC_EMIT #1635

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

Closed
wants to merge 3 commits into from
Closed

Add documentation for RUSTC_EMIT #1635

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
92c13f5
Add documentation for RUSTC_EMIT
Zoxc Mar 6, 2023
6c827aa
List emit formats and mention to modify crate files
Zoxc Mar 6, 2023
549492f
Fix some nits
Zoxc Mar 17, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions src/building/bootstrapping.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -365,6 +365,16 @@ recompiling all dependencies.
`CARGOFLAGS` will pass arguments to cargo itself (e.g. `--timings`). `CARGOFLAGS_BOOTSTRAP` and
`CARGOFLAGS_NOT_BOOTSTRAP` work analogously to `RUSTFLAGS_BOOTSTRAP`.

`RUSTC_EMIT` will cause `bootstrap` to pass `--emit` arguments on to `rustc`.
You can specify which `--emit` formats which are used with a comma separated list prefixed with
a crate name and `=`, for example: `rustc_arena=llvm-ir,asm`.
You can also substitute `*` for the crate name to apply it to all crates.
You can combine multiple such specifiers by seperating them with semi-colons like
`rustc_arena=llvm-ir,asm;rustc_span=asm;*=llvm-bc`.
The emitted files will be stored inside the `emit` directory in the target specific build directory.
`RUSTC_EMIT` will not cause `bootstrap` to rebuild any crates so you may need to modify the crates
you're interested in.

`--test-args` will pass arguments through to the test runner. For `tests/ui`, this is
compiletest; for unit tests and doctests this is the `libtest` runner. Most test runner accept
`--help`, which you can use to find out the options accepted by the runner.
Expand Down