diff options
| author | Aryadev Chavali <aryadev@aryadevchavali.com> | 2024-04-09 21:23:54 +0630 |
|---|---|---|
| committer | Aryadev Chavali <aryadev@aryadevchavali.com> | 2024-04-09 21:23:54 +0630 |
| commit | d478522d603a6257f83759d4713f222355db4af9 (patch) | |
| tree | a4506acf8179967a999baf9f0213b564f362ba14 | |
| parent | 33e1d2ab72457dcba1aa2708554705fb31de4ba3 (diff) | |
| download | ovm-d478522d603a6257f83759d4713f222355db4af9.tar.gz ovm-d478522d603a6257f83759d4713f222355db4af9.tar.bz2 ovm-d478522d603a6257f83759d4713f222355db4af9.zip | |
Some rewording of spec.org
| -rw-r--r-- | spec.org | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -6,8 +6,8 @@ * WIP Data types There are 3 main data types of the virtual machine. They are all unsigned. There exist signed versions of these data types, though -there is no difference in terms of bytecode between them. For an -unsigned type <T> the signed version is simply S_<T>. +there is no difference (internally) between them. For an unsigned +type <T> the signed version is simply S_<T>. |-------+------| | Name | Bits | |-------+------| @@ -29,9 +29,9 @@ many of A can I fit in B". |-------+------+-------+------| * WIP Instructions An instruction for the virtual machine is composed of an *opcode* and, -potentially, an *operand*. An /opcode/ represents the behaviour of -the instruction i.e. what _is_ the instruction. The /operand/ is a -datum of one of the /data types/ described previously. +potentially, an *operand*. The /opcode/ represents the behaviour of +the instruction i.e. what _is_ the instruction. The /operand/ is an +element of one of the /data types/ described previously. Some instructions do have /operands/ while others do not. The former type of instructions are called *UNIT* instructions while the latter |