oreodave/ovm
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Some rewording of spec.org

Browse Source
This commit is contained in:
Aryadev Chavali
2024-04-09 21:23:54 +06:30
parent 33e1d2ab72
commit d478522d60
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
spec.org
View File

@@ -6,8 +6,8 @@
* WIP Data types * WIP Data types
There are 3 main data types of the virtual machine. They are all There are 3 main data types of the virtual machine. They are all
unsigned. There exist signed versions of these data types, though unsigned. There exist signed versions of these data types, though
there is no difference in terms of bytecode between them. For an there is no difference (internally) between them. For an unsigned
unsigned type <T> the signed version is simply S_<T>. type <T> the signed version is simply S_<T>.
|-------+------| |-------+------|
| Name | Bits | | Name | Bits |
|-------+------| |-------+------|
@@ -29,9 +29,9 @@ many of A can I fit in B".
|-------+------+-------+------| |-------+------+-------+------|
* WIP Instructions * WIP Instructions
An instruction for the virtual machine is composed of an *opcode* and, An instruction for the virtual machine is composed of an *opcode* and,
potentially, an *operand*. An /opcode/ represents the behaviour of potentially, an *operand*. The /opcode/ represents the behaviour of
the instruction i.e. what _is_ the instruction. The /operand/ is a the instruction i.e. what _is_ the instruction. The /operand/ is an
datum of one of the /data types/ described previously. element of one of the /data types/ described previously.
Some instructions do have /operands/ while others do not. The former Some instructions do have /operands/ while others do not. The former
type of instructions are called *UNIT* instructions while the latter type of instructions are called *UNIT* instructions while the latter