riscv
/
binutils-gdb
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
106707 Commits
163 Branches
728 Tags
638 MiB
 
 
 
 
 
 
Tree: ce3ec98acd
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'ce3ec98acd'
${ noResults }
binutils-gdb/sim/example-synacor
Mike Frysinger ce3ec98acd
sim: unify gettext/intl probing logic 		5 years ago
..
ChangeLog sim: unify bfd library dependency testing logic 5 years ago
Makefile.in sim: example-synacor: a simple implementation for reference 5 years ago
README sim: example-synacor: a simple implementation for reference 5 years ago
README.arch-spec sim: example-synacor: a simple implementation for reference 5 years ago
aclocal.m4 sim: unify gettext/intl probing logic 5 years ago
configure sim: unify gettext/intl probing logic 5 years ago
configure.ac sim: overhaul & unify endian settings management 5 years ago
interp.c sim: overhaul & unify endian settings management 5 years ago
sim-main.c sim: split sim-signal.h include out 5 years ago
sim-main.h sim: fully merge sim_state_base into sim_state 5 years ago

README 

= OVERVIEW =

The Synacor Challenge is a fun programming exercise with a number of puzzles
built into it.  You can find more details about it here:
https://challenge.synacor.com/

The first puzzle is writing an interpreter for their custom ISA.  This is a
simulator for that custom CPU.  The CPU is quite basic: it's 16-bit with only
8 registers and a limited set of instructions.  This means the port will never
grow new features.  See README.arch-spec for more details.

Implementing it here ends up being quite useful: it acts as a simple constrained
"real world" example for people who want to implement a new simulator for their
own architecture.  We demonstrate all the basic fundamentals (registers, memory,
branches, and tracing) that all ports should have.