From fe44fdae1845b5be8a16253664937a559a24503a Mon Sep 17 00:00:00 2001 From: Ali Nazzal Date: Thu, 28 Aug 2025 19:00:47 +0300 Subject: [PATCH] dates(infra): refresh date-check annotations for Aug 2025; preserve local style --- src/backend/updating-llvm.md | 4 ++-- src/fuzzing.md | 2 +- src/overview.md | 2 +- src/parallel-rustc.md | 8 ++++---- src/profiling.md | 2 +- src/rustdoc-internals.md | 6 +++--- 6 files changed, 12 insertions(+), 12 deletions(-) diff --git a/src/backend/updating-llvm.md b/src/backend/updating-llvm.md index ebef15d40..a4e22b739 100644 --- a/src/backend/updating-llvm.md +++ b/src/backend/updating-llvm.md @@ -1,6 +1,6 @@ # Updating LLVM - + Rust supports building against multiple LLVM versions: * Tip-of-tree for the current LLVM development branch is usually supported @@ -93,7 +93,7 @@ An example PR: ## New LLVM Release Updates - + Unlike bugfixes, updating to a new release of LLVM typically requires a lot more work. diff --git a/src/fuzzing.md b/src/fuzzing.md index 300053786..540a8c690 100644 --- a/src/fuzzing.md +++ b/src/fuzzing.md @@ -1,6 +1,6 @@ # Fuzzing - + For the purposes of this guide, *fuzzing* is any testing methodology that involves compiling a wide variety of programs in an attempt to uncover bugs in diff --git a/src/overview.md b/src/overview.md index 378d8c445..9f0201942 100644 --- a/src/overview.md +++ b/src/overview.md @@ -304,7 +304,7 @@ Moreover, the compiler wasn't originally built to use a query system; the query system has been retrofitted into the compiler, so parts of it are not query-fied yet. Also, LLVM isn't our code, so that isn't querified either. The plan is to eventually query-fy all of the steps listed in the previous section, -but as of November 2022, only the steps between `HIR` and +but as of August 2025, only the steps between `HIR` and `LLVM-IR` are query-fied. That is, lexing, parsing, name resolution, and macro expansion are done all at once for the whole program. diff --git a/src/parallel-rustc.md b/src/parallel-rustc.md index ce69b66c2..b44824322 100644 --- a/src/parallel-rustc.md +++ b/src/parallel-rustc.md @@ -1,14 +1,14 @@ # Parallel compilation
-As of November 2024, +As of August 2025, the parallel front-end is undergoing significant changes, so this page contains quite a bit of outdated information. Tracking issue:
-As of November 2024, most of the rust compiler is now +As of August 2025, most of the rust compiler is now parallelized. - The codegen part is executed concurrently by default. You can use the `-C @@ -104,7 +104,7 @@ when `parallel-compiler` is true. | **ModuleItems::par_foreign_items**(&self, f: impl Fn(ForeignItemId)) | run `f` on all foreign items in the module | rustc_middle::hir | There are a lot of loops in the compiler which can possibly be parallelized -using these functions. As of August 2022, scenarios where +using these functions. As of August 2025, scenarios where the parallel iterator function has been used are as follows: | caller | scenario | callee | @@ -155,7 +155,7 @@ open feature tracking issue][tracking]. ## Rustdoc -As of November 2022, there are still a number of steps to +As of August 2025, there are still a number of steps to complete before `rustdoc` rendering can be made parallel (see a open discussion of [parallel `rustdoc`][parallel-rustdoc]). diff --git a/src/profiling.md b/src/profiling.md index de06bd7cd..7dfd74aba 100644 --- a/src/profiling.md +++ b/src/profiling.md @@ -108,6 +108,6 @@ The llvm-lines output is affected by several options. MIR optimizations have little impact. Compared to the default `RUSTFLAGS="-Z mir-opt-level=1"`, level 0 adds 0.3GB and level 2 removes 0.2GB. -As of July 2022, +As of August 2025, inlining happens in LLVM and GCC codegen backends, missing only in the Cranelift one. diff --git a/src/rustdoc-internals.md b/src/rustdoc-internals.md index 4affbafe4..02abce2e6 100644 --- a/src/rustdoc-internals.md +++ b/src/rustdoc-internals.md @@ -99,7 +99,7 @@ regarding dropping private/hidden items can be bypassed by passing `--document-private-items` to `rustdoc`. Note that unlike the previous set of [`AST`][ast] transformations, the passes are run on the _cleaned_ crate. -Here is the list of passes as of March 2023: +Here is the list of passes as of August 2025: - `calculate-doc-coverage` calculates information used for the `--show-coverage` flag. @@ -122,7 +122,7 @@ Here is the list of passes as of March 2023: - `bare_urls` detects links that are not linkified, e.g., in Markdown such as `Go to https://example.com/.` It suggests wrapping the link with angle brackets: `Go to .` to linkify it. This is the code behind the `rustdoc::bare_urls` `lint`. + date-check: Aug 2025 --> `rustdoc::bare_urls` `lint`. - `check_code_block_syntax` validates syntax inside Rust code blocks (```rust) @@ -212,7 +212,7 @@ directly, even during `HTML` generation. This [didn't used to be the case], and a lot of `rustdoc`'s architecture was designed around not doing that, but a `TyCtxt` is now passed to `formats::renderer::run_format`, which is used to run generation for both `HTML` and the -(unstable as of March 2023) JSON format. +(unstable as of August 2025) JSON format. This change has allowed other changes to remove data from the "clean" [`AST`][ast] that can be easily derived from `TyCtxt` queries, and we'll usually accept