Commit d44cac5

committed

Auto merge of #145600 - jieyouxu:rollup-jw0bpnt, r=jieyouxu

Rollup of 15 pull requests Successful merges: - rust-lang/rust#145338 (actually provide the correct args to coroutine witnesses) - rust-lang/rust#145429 (Couple of codegen_fn_attrs improvements) - rust-lang/rust#145452 (Do not strip binaries in bootstrap everytime if they are unchanged) - rust-lang/rust#145464 (Stabilize `const_pathbuf_osstring_new` feature) - rust-lang/rust#145474 (Properly recover from parenthesized use-bounds (precise capturing lists) plus small cleanups) - rust-lang/rust#145486 (Fix `unicode_data.rs` mention message) - rust-lang/rust#145490 (Trace some basic I/O operations in bootstrap) - rust-lang/rust#145493 (remove `should_render` in `PrintAttribute` derive) - rust-lang/rust#145500 (Port must_use to the new target checking) - rust-lang/rust#145505 (Simplify span caches) - rust-lang/rust#145510 (Visit and print async_fut local for async drop.) - rust-lang/rust#145511 (Rust build fails on OpenBSD after using file_lock feature) - rust-lang/rust#145532 (resolve: debug for block module) - rust-lang/rust#145533 (Reorder `lto` options from most to least optimizing) - rust-lang/rust#145537 (Do not consider a `T: !Sized` candidate to satisfy a `T: !MetaSized` obligation.) r? `@ghost` `@rustbot` modify labels: rollup

2 parents 2db7146 + 69b8a6f commit d44cac5Copy full SHA for d44cac5

File tree

1 file changed

-3

lines changed

src/building/bootstrapping
- debugging-bootstrap.md

1 file changed

-3

lines changed

`‎src/building/bootstrapping/debugging-bootstrap.md‎`

Lines changed: 5 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -81,9 +81,11 @@ There are two orthogonal ways to control which kind of tracing logs you want:`
`81`	`81`	`- If you select a level, all events/spans with an equal or higher priority level will be shown.`
`82`	`82`	2. You can also control the log target, e.g. `bootstrap` or `bootstrap::core::config` or a custom target like `CONFIG_HANDLING` or `STEP`.
`83`	`83`	- Custom targets are used to limit what kinds of spans you are interested in, as the `BOOTSTRAP_TRACING=trace` output can be quite verbose. Currently, you can use the following custom targets:
`84`		- - `CONFIG_HANDLING`: show spans related to config handling
`85`		- - `STEP`: show all executed steps. Note that executed commands have `info` event level.
`86`		- - `COMMAND`: show all executed commands. Note that executed commands have `trace` event level.
	`84`	+ - `CONFIG_HANDLING`: show spans related to config handling.
	`85`	+ - `STEP`: show all executed steps. Executed commands have `info` event level.
	`86`	+ - `COMMAND`: show all executed commands. Executed commands have `trace` event level.
	`87`	+ - `IO`: show performed I/O operations. Executed commands have `trace` event level.
	`88`	`+ - Note that many I/O are currently not being traced.`
`87`	`89`
`88`	`90`	You can of course combine them (custom target logs are typically gated behind `TRACE` log level additionally):
`89`	`91`

0 commit comments

Comments

(0)

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit d44cac5

File tree

1 file changed

1 file changed

`‎src/building/bootstrapping/debugging-bootstrap.md‎`

0 commit comments