gh-119786: Fix miscellaneous typos in InternalDocs/interpreter_definition.md (#127957)

This commit is contained in:
Stan Ulbrych 2024-12-15 17:11:50 +00:00 committed by GitHub
parent 3683b2f9e5
commit 7b8bd3b2b8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -174,7 +174,7 @@ list of annotations and their meanings are as follows:
* `override`. For external use by other interpreter definitions to override the current
instruction definition.
* `pure`. This instruction has no side effects.
* 'tierN'. This instruction only used by tier N interpreter.
* 'tierN'. This instruction is only used by the tier N interpreter.
### Special functions/macros
@ -393,7 +393,7 @@ which can be easily inserted. What is more complex is ensuring the correct stack
and not generating excess pops and pushes.
For example, in `CHECK_HAS_INSTANCE_VALUES`, `owner` occurs in the input, so it cannot be
redefined. Thus it doesn't need to be written and can be read without adjusting the stack pointer.
redefined. Thus, it doesn't need to be written and can be read without adjusting the stack pointer.
The C code generated for `CHECK_HAS_INSTANCE_VALUES` would look something like:
```C
@ -404,7 +404,7 @@ The C code generated for `CHECK_HAS_INSTANCE_VALUES` would look something like:
}
```
When combining ops together to form instructions, temporary values should be used,
When combining ops to form instructions, temporary values should be used,
rather than popping and pushing, such that `LOAD_ATTR_SLOT` would look something like:
```C