Docs: fix spelling of the word 'transferring' (#116641)

This commit is contained in:
guangwu 2024-03-14 06:53:32 +08:00 committed by GitHub
parent cef0ec1a3c
commit 7af4b9f253
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions

View File

@ -52,7 +52,7 @@ The JIT compiler converts superblocks into machine code executors.
These have identical behavior to interpreted executors, except that These have identical behavior to interpreted executors, except that
they consume more memory for the generated machine code and are a lot faster. they consume more memory for the generated machine code and are a lot faster.
## Transfering control ## Transferring control
There are three types of control transfer that we need to consider: There are three types of control transfer that we need to consider:
* Tier 1 to tier 2 * Tier 1 to tier 2
@ -104,7 +104,7 @@ reference to the previous executor in the thread state's
#### The interpreter #### The interpreter
The tier 2 interpreter has a variable `current_executor` which The tier 2 interpreter has a variable `current_executor` which
points to the currently live executor. When transfering from executor points to the currently live executor. When transferring from executor
`A` to executor `B` we do the following: `A` to executor `B` we do the following:
(Initially `current_executor` points to `A`, and the refcount of (Initially `current_executor` points to `A`, and the refcount of
`A` is elevated by one) `A` is elevated by one)
@ -122,7 +122,7 @@ increment the refcount of `B` and set `current_executor` to point to `B`.
#### In the JIT #### In the JIT
Transfering control from one executor to another is done via tailcalls. Transferring control from one executor to another is done via tailcalls.
The compiled executor should do the same, except that there is no local The compiled executor should do the same, except that there is no local
variable `current_executor`. variable `current_executor`.