Rustc pull update #2551

Original file line number	Diff line number	Diff line change
Expand Up		@@ -17,7 +17,7 @@ fn main() {

		The detailed documentation for the `std::autodiff` module is available at [std::autodiff](https://doc.rust-lang.org/std/autodiff/index.html).

	Differentiable programing is used in various fields like numerical computing, [solid mechanics][ratel], [computational chemistry][molpipx], [fluid dynamics][waterlily] or for Neural Network training via Backpropagation, [ODE solver][diffsol], [differentiable rendering][libigl], [quantum computing][catalyst], and climate simulations.
	Differentiable programming is used in various fields like numerical computing, [solid mechanics][ratel], [computational chemistry][molpipx], [fluid dynamics][waterlily] or for Neural Network training via Backpropagation, [ODE solver][diffsol], [differentiable rendering][libigl], [quantum computing][catalyst], and climate simulations.

		[ratel]: https://gitlab.com/micromorph/ratel
		[molpipx]: https://arxiv.org/abs/2411.17011v
Expand Down

8 changes: 5 additions & 3 deletions src/building/bootstrapping/debugging-bootstrap.md

Show comments View file Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -81,9 +81,11 @@ There are two orthogonal ways to control which kind of tracing logs you want:
		- If you select a level, all events/spans with an equal or higher priority level will be shown.
		2. You can also control the log target, e.g. `bootstrap` or `bootstrap::core::config` or a custom target like `CONFIG_HANDLING` or `STEP`.
		- 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:
	- `CONFIG_HANDLING`: show spans related to config handling
	- `STEP`: show all executed steps. Note that executed commands have `info` event level.
	- `COMMAND`: show all executed commands. Note that executed commands have `trace` event level.
	- `CONFIG_HANDLING`: show spans related to config handling.
	- `STEP`: show all executed steps. Executed commands have `info` event level.
	- `COMMAND`: show all executed commands. Executed commands have `trace` event level.
	- `IO`: show performed I/O operations. Executed commands have `trace` event level.
	- Note that many I/O are currently not being traced.

		You can of course combine them (custom target logs are typically gated behind `TRACE` log level additionally):

Expand Down

2 changes: 1 addition & 1 deletion src/sanitizers.md

Show comments View file Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -45,7 +45,7 @@ implementation:
		[marked][sanitizer-attribute] with appropriate LLVM attribute:
		`SanitizeAddress`, `SanitizeHWAddress`, `SanitizeMemory`, or
		`SanitizeThread`. By default all functions are instrumented, but this
	behaviour can be changed with `#[no_sanitize(...)]`.
	behaviour can be changed with `#[sanitize(xyz = "on\|off")]`.

		* The decision whether to perform instrumentation or not is possible only at a
		function granularity. In the cases were those decision differ between
Expand Down

2 changes: 1 addition & 1 deletion src/solve/candidate-preference.md

Show comments View file Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -95,7 +95,7 @@ fn overflow<T: Trait>() {
		```

		This preference causes a lot of issues. See [#24066]. Most of the
	issues are caused by prefering where-bounds over impls even if the where-bound guides type inference:
	issues are caused by preferring where-bounds over impls even if the where-bound guides type inference:
		```rust
		trait Trait<T> {
		fn call_me(&self, x: T) {}
Expand Down

1 change: 1 addition & 0 deletions src/tests/directives.md

Show comments View file Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -111,6 +111,7 @@ for more details.
		\| `forbid-output` \| A pattern which must not appear in stderr/`cfail` output \| `ui`, `incremental` \| Regex pattern \|
		\| `run-flags` \| Flags passed to the test executable \| `ui` \| Arbitrary flags \|
		\| `known-bug` \| No error annotation needed due to known bug \| `ui`, `crashes`, `incremental` \| Issue number `#123456` \|
	\| `compare-output-by-lines` \| Compare the output by lines, rather than as a single string \| All \| N/A \|

		[^check_stdout]: presently <!-- date-check: Oct 2024 --> this has a weird quirk
		where the test binary's stdout and stderr gets concatenated and then
Expand Down

1 change: 1 addition & 0 deletions src/tests/ui.md

Show comments View file Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -95,6 +95,7 @@ will check for output files:
		[Normalization](#normalization)).
		- `dont-check-compiler-stderr` — Ignores stderr from the compiler.
		- `dont-check-compiler-stdout` — Ignores stdout from the compiler.
	- `compare-output-by-lines` — Some tests have non-deterministic orders of output, so we need to compare by lines.

		UI tests run with `-Zdeduplicate-diagnostics=no` flag which disables rustc's
		built-in diagnostic deduplication mechanism. This means you may see some
Expand Down

Navigation Menu