diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2021-04-15 01:27:56 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-04-15 01:27:56 +0200 |
| commit | fd105db77279113f736762f27b25279daffd5974 (patch) | |
| tree | 46ad7c0c593440334e099029f38c266e439727ec | |
| parent | ef6704529aa59151af301d106156d635ba01cd5c (diff) | |
| parent | 26da4b43554482f5a25f79a3923f46bfe5cacd41 (diff) | |
| download | rust-fd105db77279113f736762f27b25279daffd5974.tar.gz rust-fd105db77279113f736762f27b25279daffd5974.zip | |
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.
| -rw-r--r-- | compiler/rustc_codegen_ssa/src/back/write.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/compiler/rustc_codegen_ssa/src/back/write.rs b/compiler/rustc_codegen_ssa/src/back/write.rs index 04d06864ee1..c8688faa80b 100644 --- a/compiler/rustc_codegen_ssa/src/back/write.rs +++ b/compiler/rustc_codegen_ssa/src/back/write.rs @@ -1094,7 +1094,7 @@ fn start_executing_work<B: ExtraBackendMethods>( // only place where we have access to the compiler `Session`. // - LLVM work can be done on any thread. // - Codegen can only happen on the main thread. - // - Each thread doing substantial work most be in possession of a `Token` + // - Each thread doing substantial work must be in possession of a `Token` // from the `Jobserver`. // - The compiler process always holds one `Token`. Any additional `Tokens` // have to be requested from the `Jobserver`. @@ -1146,7 +1146,7 @@ fn start_executing_work<B: ExtraBackendMethods>( // if possible. These two goals are at odds with each other: If memory // consumption were not an issue, we could just let the main thread produce // LLVM WorkItems at full speed, assuring maximal utilization of - // Tokens/LLVM worker threads. However, since codegen usual is faster + // Tokens/LLVM worker threads. However, since codegen is usually faster // than LLVM processing, the queue of LLVM WorkItems would fill up and each // WorkItem potentially holds on to a substantial amount of memory. // |
