Merge pull request #21419 from rust-lang/rustc-pull

Rustc pull update

Author: lnicola

.github/workflows/date-check.yml

@@ -22,9 +22,7 @@ jobs:
           rustup update stable
 
       - name: Run `date-check`
-        working-directory: ci/date-check
-        run: |
-          cargo run -- ../../src/ > ../../date-check-output.txt
+        run: cargo run --manifest-path ci/date-check/Cargo.toml . > date-check-output.txt
 
       - name: Open issue
         uses: actions/github-script@v7

ci/date-check/src/main.rs

@@ -153,9 +153,13 @@ fn main() {
         println!();
 
         for (path, dates) in dates_by_file {
-            println!("- {}", path.strip_prefix(&root_dir_path).unwrap_or(&path).display(),);
+            let path = path.strip_prefix(&root_dir_path).unwrap_or(&path).display();
+            println!("- {path}");
             for (line, date) in dates {
-                println!("  - [ ] line {}: {}", line, date);
+                let url = format!(
+                    "https://github.com/rust-lang/rustc-dev-guide/blob/main/{path}?plain=1#L{line}"
+                );
+                println!("  - [ ] {date} [line {line}]({url})");
             }
         }
         println!();

rust-version

@@ -1 +1 @@
-2dc30247c5d8293aaa31e1d7dae2ed2fde908ada
+85c8ff69cb3efd950395cc444a54bbbdad668865

src/SUMMARY.md

@@ -100,7 +100,7 @@
 - [Parallel compilation](./parallel-rustc.md)
 - [Rustdoc internals](./rustdoc-internals.md)
     - [Search](./rustdoc-internals/search.md)
-	- [The `rustdoc` test suite](./rustdoc-internals/rustdoc-test-suite.md)
+	- [The `rustdoc-html` test suite](./rustdoc-internals/rustdoc-html-test-suite.md)
 	- [The `rustdoc-gui` test suite](./rustdoc-internals/rustdoc-gui-test-suite.md)
 	- [The `rustdoc-json` test suite](./rustdoc-internals/rustdoc-json-test-suite.md)
 - [GPU offload internals](./offload/internals.md)

src/getting-started.md

@@ -179,7 +179,7 @@ The following tasks are doable without much background knowledge but are incredi
   to read a part of the code and write doc comments for it.
   This will help you to learn some part of the compiler while also producing a useful artifact!
 - [Triaging issues][triage]: categorizing, replicating, and minimizing issues is very helpful to the Rust maintainers.
-- [Working groups][wg]: there are a bunch of working groups on a wide variety
+- [Working areas][wa]: there are a bunch of working areas on a wide variety
   of rust-related things.
 - Answer questions on [users.rust-lang.org][users], or on [Stack Overflow][so].
 - Participate in the [RFC process](https://github.com/rust-lang/rfcs).
@@ -191,7 +191,7 @@ The following tasks are doable without much background knowledge but are incredi
 [so]: http://stackoverflow.com/questions/tagged/rust
 [community-library]: https://github.com/rust-lang/rfcs/labels/A-community-library
 [wd]: ./contributing.md#writing-documentation
-[wg]: https://rust-lang.github.io/compiler-team/working-groups/
+[wa]: https://forge.rust-lang.org/compiler/working-areas.html
 [triage]: ./contributing.md#issue-triage
 
 ## Cloning and Building

src/offload/usage.md

@@ -57,7 +57,7 @@ fn main() {
 
 #[inline(never)]
 unsafe fn kernel(x: *mut [f64; 256]) {
-    core::intrinsics::offload(kernel_1, (x,))
+    core::intrinsics::offload(_kernel_1, [256, 1, 1], [32, 1, 1], (x,))
 }
 
 #[cfg(target_os = "linux")]

src/overview.md

@@ -50,10 +50,10 @@ preserves full fidelity information for both IDEs and procedural macros
 The *parser* [translates the token stream from the `lexer` into an Abstract Syntax
 Tree (AST)][parser]. It uses a recursive descent (top-down) approach to syntax
 analysis. The crate entry points for the `parser` are the
-[`Parser::parse_crate_mod()`][parse_crate_mod] and [`Parser::parse_mod()`][parse_mod]
+[`Parser::parse_crate_mod`][parse_crate_mod] and [`Parser::parse_mod`][parse_mod]
 methods found in [`rustc_parse::parser::Parser`]. The external module parsing
 entry point is [`rustc_expand::module::parse_external_mod`][parse_external_mod].
-And the macro-`parser` entry point is [`Parser::parse_nonterminal()`][parse_nonterminal].
+And the macro-`parser` entry point is [`Parser::parse_nonterminal`][parse_nonterminal].
 
 Parsing is performed with a set of [`parser`] utility methods including [`bump`],
 [`check`], [`eat`], [`expect`], [`look_ahead`].

…/rustdoc-internals/rustdoc-test-suite.md …doc-internals/rustdoc-html-test-suite.mdsrc/rustdoc-internals/rustdoc-test-suite.md renamed to src/rustdoc-internals/rustdoc-html-test-suite.md src/rustdoc-internals/rustdoc-test-suite.md renamed to src/rustdoc-internals/rustdoc-html-test-suite.md

@@ -1,6 +1,6 @@
-# The `rustdoc` test suite
+# The `rustdoc-html` test suite
 
-This page is about the test suite named `rustdoc` used to test the HTML output of `rustdoc`.
+This page is about the test suite named `rustdoc-html` used to test the HTML output of `rustdoc`.
 For other rustdoc-specific test suites, see [Rustdoc test suites].
 
 Each test file in this test suite is simply a Rust source file `file.rs` sprinkled with

src/rustdoc-internals/rustdoc-json-test-suite.md

@@ -24,7 +24,7 @@ Also, talk about how it works
 ## jsondocck
 
 [jsondocck] processes directives given in comments, to assert that the values in the output are expected.
-It's a lot like [htmldocck](./rustdoc-test-suite.md) in that way.
+It's a lot like [htmldocck](./rustdoc-html-test-suite.md) in that way.
 
 It uses [JSONPath] as a query language, which takes a path, and returns a *list* of values that that path is said to match to.
 

src/tests/best-practices.md

@@ -153,6 +153,7 @@ This may include remarks on:
 - Try to make sure the test is as minimal as possible.
 - Minimize non-critical code and especially minimize unnecessary syntax and type
   errors which can clutter stderr snapshots.
+- Use `#![allow(...)]` or `#![expect(...)]` to suppress unrelated warnings.
 - Where possible, use semantically meaningful names (e.g. `fn
   bare_coverage_attributes() {}`).