martinbrugnara / archetypum Goto Github PK

Meaningful default config values

Display for each instruction its execution status.
For example something like: <age>/<instr_duration>

NOTE: the representation in the slides may be misleading -> each FU should have its own "aging pipeline".

• reservation stations: split multiplier from divider, since they may have different durations
• memory: remove offset from LDR operation so that it will get 2 parameters as inputs (like STR)
• extra: keyboard bindings for play/pause/step/reset/speed
• registry: show id of who is going to write in that entry
• branch predictor: add address tag
• cache: read & write of entire line made of more than one block

Visualizator -> visualizer

Chrome & firefox are fine. Probably some ES6 feature isn't supported by safari.

Once ROB #3 is in place, implement most relevant branch prediction algorithms.

The store operation has to be executed only by the ROB during commit phase, since it modifies the memory
#3

in source code tab add help: list of available instruction an format.

Memory abstraction is required for cache emulation, and for LOAD and STORE instructions.

Specs:

• Reading from uninitialized memory loc. returns random value
• Reading from a previously written memory loc. returns consistent value.

Plus:

• Memory latency is programmable

Once memory abstraction is in place #1 , add support for cache emulation.

Kind:

• No cache
• Decide which to should be implement.
  Once the interface is defined external contribution are really welcomed here (easy but meany possibilities)
• n-way set associative (non concurrent)

meaningful default examples

Implement Reorder Buffer (ROB) to allow control flow instruction (JMP, JEQ,...)

Flush strategy: once head of circular buffer flush
FLAG register: when commit update FLAG register.

• non resizable raw-src txtarea

cast division outcome to int