Skip to content

Navigation Menu

Sign in
Appearance settings

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

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit 896fed3

Browse files
Revert "dates: refresh infra/tooling date annotations to Aug 2025"
1 parent 1d08585 commit 896fed3

File tree

6 files changed

+12
-12
lines changed

6 files changed

+12
-12
lines changed

‎src/backend/updating-llvm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Updating LLVM
22

3-
<!-- date-check: Aug 2025 -->
3+
<!-- date-check: Aug 2024 -->
44
Rust supports building against multiple LLVM versions:
55

66
* Tip-of-tree for the current LLVM development branch is usually supported
@@ -93,7 +93,7 @@ An example PR:
9393

9494
## New LLVM Release Updates
9595

96-
<!-- date-check: Aug 2025 -->
96+
<!-- date-check: Jul 2023 -->
9797

9898
Unlike bugfixes,
9999
updating to a new release of LLVM typically requires a lot more work.

‎src/fuzzing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Fuzzing
22

3-
<!-- date-check: Aug 2025 -->
3+
<!-- date-check: Mar 2023 -->
44

55
For the purposes of this guide, *fuzzing* is any testing methodology that
66
involves compiling a wide variety of programs in an attempt to uncover bugs in

‎src/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -304,7 +304,7 @@ Moreover, the compiler wasn't originally built to use a query system; the query
304304
system has been retrofitted into the compiler, so parts of it are not query-fied
305305
yet. Also, LLVM isn't our code, so that isn't querified either. The plan is to
306306
eventually query-fy all of the steps listed in the previous section,
307-
but as of <!-- date-check --> August 2025, only the steps between `HIR` and
307+
but as of <!-- date-check --> November 2022, only the steps between `HIR` and
308308
`LLVM-IR` are query-fied. That is, lexing, parsing, name resolution, and macro
309309
expansion are done all at once for the whole program.
310310

‎src/parallel-rustc.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# Parallel compilation
22

33
<div class="warning">
4-
As of <!-- date-check --> August 2025,
4+
As of <!-- date-check --> November 2024,
55
the parallel front-end is undergoing significant changes,
66
so this page contains quite a bit of outdated information.
77

88
Tracking issue: <https://github.com/rust-lang/rust/issues/113349>
99
</div>
1010

11-
As of <!-- date-check --> August 2025, most of the rust compiler is now
11+
As of <!-- date-check --> November 2024, most of the rust compiler is now
1212
parallelized.
1313

1414
- The codegen part is executed concurrently by default. You can use the `-C
@@ -104,7 +104,7 @@ when `parallel-compiler` is true.
104104
| **ModuleItems::par_foreign_items**(&self, f: impl Fn(ForeignItemId)) | run `f` on all foreign items in the module | rustc_middle::hir |
105105

106106
There are a lot of loops in the compiler which can possibly be parallelized
107-
using these functions. As of <!-- date-check--> August 2025, scenarios where
107+
using these functions. As of <!-- date-check--> August 2022, scenarios where
108108
the parallel iterator function has been used are as follows:
109109

110110
| caller | scenario | callee |
@@ -155,7 +155,7 @@ open feature tracking issue][tracking].
155155

156156
## Rustdoc
157157

158-
As of <!-- date-check--> August 2025, there are still a number of steps to
158+
As of <!-- date-check--> November 2022, there are still a number of steps to
159159
complete before `rustdoc` rendering can be made parallel (see a open discussion
160160
of [parallel `rustdoc`][parallel-rustdoc]).
161161

‎src/profiling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,6 @@ The llvm-lines output is affected by several options.
108108

109109
MIR optimizations have little impact. Compared to the default `RUSTFLAGS="-Z
110110
mir-opt-level=1"`, level 0 adds 0.3GB and level 2 removes 0.2GB.
111-
As of <!-- date-check --> August 2025,
111+
As of <!-- date-check --> July 2022,
112112
inlining happens in LLVM and GCC codegen backends,
113113
missing only in the Cranelift one.

‎src/rustdoc-internals.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ regarding dropping private/hidden items can be bypassed by passing
9999
`--document-private-items` to `rustdoc`. Note that unlike the previous set of [`AST`][ast]
100100
transformations, the passes are run on the _cleaned_ crate.
101101

102-
Here is the list of passes as of <!-- date-check --> August 2025:
102+
Here is the list of passes as of <!-- date-check --> March 2023:
103103

104104
- `calculate-doc-coverage` calculates information used for the `--show-coverage`
105105
flag.
@@ -122,7 +122,7 @@ Here is the list of passes as of <!-- date-check --> August 2025:
122122
- `bare_urls` detects links that are not linkified, e.g., in Markdown such as
123123
`Go to https://example.com/.` It suggests wrapping the link with angle brackets:
124124
`Go to <https://example.com/>.` to linkify it. This is the code behind the <!--
125-
date-check: Aug 2025 --> `rustdoc::bare_urls` `lint`.
125+
date-check: may 2022 --> `rustdoc::bare_urls` `lint`.
126126

127127
- `check_code_block_syntax` validates syntax inside Rust code blocks
128128
(<code>```rust</code>)
@@ -212,7 +212,7 @@ directly, even during `HTML` generation. This [didn't used to be the case], and
212212
a lot of `rustdoc`'s architecture was designed around not doing that, but a
213213
`TyCtxt` is now passed to `formats::renderer::run_format`, which is used to
214214
run generation for both `HTML` and the
215-
(unstable as of <!-- date-check --> August 2025) JSON format.
215+
(unstable as of <!-- date-check --> March 2023) JSON format.
216216

217217
This change has allowed other changes to remove data from the "clean" [`AST`][ast]
218218
that can be easily derived from `TyCtxt` queries, and we'll usually accept

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /