Differences

This shows you the differences between two versions of the page.

--- projects:archevo:isa [2021/04/20 02:57] – Owen Mellema
+++ projects:archevo:isa [2021/04/21 00:03] (current) – [ISAs in ArchEvo] Owen Mellema
@@ Line 3: / Line 3: @@
 ===== What is an ISA? =====
-An //ISA//, short for Instruction Set Architecture, is the convention that allows programmers to talk to computers. The programmer can write a string of bits, give it to a CPU, and the CPU will do something. It is the most basic form of programming language. In fact, all programming languages are eventually turned into a series of bits based off of the ISA. 9The series of bits is sometimes called Assembly Language, but that isn't important here.)
+An //ISA//, short for Instruction Set Architecture, is the convention that allows programmers to talk to computers. The programmer can write a string of bits, give it to a CPU, and the CPU will do something. It is the most basic form of programming language. In fact, all programming languages are eventually turned into a series of bits based off of the ISA. (The series of bits is sometimes called Assembly Language, but that isn't important here.)
 ===== Brittleness =====
-ISAs that are practically used are generally //brittle//. This means that if a random bit flips in an instruction, the results will likely be catastrophic (for the execution of the program, that is). Although this isn't a purposeful choice on the parts of the designers of these ISAs, it isn't necessarily a bad thing. Consider, for example, an ATM. if a "cosmic ray" hits the CPU, and an instruction has a bit flip, we (or, at least, the bankers) don't want it to continue running as if nothing had happened, as this could lead to a loss of money. Instead, they would rather the program fail, and just be rebooted.
+ISAs that are practically used are generally //brittle//. This means that if a random bit flips in an instruction, the results will likely be catastrophic (for the execution of the program, that is). Although this isn't a purposeful choice on the parts of the designers of these ISAs, it isn't necessarily a bad thing. Consider, for example, an ATM. If a "cosmic ray" hits the CPU, and an instruction has a bit flip, we (or, at least, the bankers) don't want it to continue running as if nothing had happened, as this could lead to a loss of money. Instead, they would rather the program fail, and just be rebooted.
 Brittleness is caused by two main factors.
@@ Line 74: / Line 74: @@
 ==== IPLOC ====
-One problem with
+In order for cells to be able to observe other cells' registers, they must be able to manipulate an offset to that cell. We can limit this to the eight adjacent squares around a cell to make this easier.
+The naïve approach would be to store each offset as a number in a register. There are two problems with this. Firstly, interpreting the register as an unsigned int, the possible range for observation becomes a square of size 256 around the cell. This is not what we want. Secondly, this requires two registers, which is not ideal.
+The IPLOC (**I**nspection **P**ointer **LOC**ation) convention circumvents this by encoding each of the eight offsets as a bit in a single register. The actual offset is the most significant bit in the register.
+<code>
+xxxxxxx => ( 1,  1)
+xxxxxx => ( 0,  1)
+xxxxx => (-1,  1)
+xxxx => ( 1,  0)
+xxx => (-1,  0)
+xx => ( 1, -1)
+0000001x => ( 0, -1)
+00000001 => (-1, -1)
+00000000 => ( 0,  0)
+</code>
+===== ISAs in ArchEvo =====
+The following is a list of the ISAs in ArchEvo:
+  * [[projects:archevo:asia|ASIA]]