Skip to content

Commit fd105db

Browse files
authored
Rollup merge of #84192 - vext01:backend-write-typos, r=wesleywiser
Fix typos in rustc_codegen_ssa/src/back/write.rs. Just a couple of typos I spotted when reading this comment about the job server.
2 parents ef67045 + 26da4b4 commit fd105db

File tree

1 file changed

+2
-2
lines changed
  • compiler/rustc_codegen_ssa/src/back

1 file changed

+2
-2
lines changed

compiler/rustc_codegen_ssa/src/back/write.rs

+2-2
Original file line numberDiff line numberDiff line change
@@ -1094,7 +1094,7 @@ fn start_executing_work<B: ExtraBackendMethods>(
10941094
// only place where we have access to the compiler `Session`.
10951095
// - LLVM work can be done on any thread.
10961096
// - Codegen can only happen on the main thread.
1097-
// - Each thread doing substantial work most be in possession of a `Token`
1097+
// - Each thread doing substantial work must be in possession of a `Token`
10981098
// from the `Jobserver`.
10991099
// - The compiler process always holds one `Token`. Any additional `Tokens`
11001100
// have to be requested from the `Jobserver`.
@@ -1146,7 +1146,7 @@ fn start_executing_work<B: ExtraBackendMethods>(
11461146
// if possible. These two goals are at odds with each other: If memory
11471147
// consumption were not an issue, we could just let the main thread produce
11481148
// LLVM WorkItems at full speed, assuring maximal utilization of
1149-
// Tokens/LLVM worker threads. However, since codegen usual is faster
1149+
// Tokens/LLVM worker threads. However, since codegen is usually faster
11501150
// than LLVM processing, the queue of LLVM WorkItems would fill up and each
11511151
// WorkItem potentially holds on to a substantial amount of memory.
11521152
//

0 commit comments

Comments
 (0)