Efthimis/Testing
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Just to test the server
53 Commits 1 Branch 1 Tag 294 KiB
SVG 100%
master
Go to file
(Tim) Efthimis Kritikos e38cb21738 check email change
2024-02-01 15:27:27 +00:00
.test6.md.swp Another test 2023-02-19 00:32:09 +00:00
9086_overview.svg Test 2023-05-03 17:39:01 +01:00
9086_v0.2.0.svg More tests 2023-10-23 13:22:24 +01:00
9086.svg Test 2023-10-24 01:04:25 +01:00
README.md check email change 2024-02-01 15:27:27 +00:00
test2.md Efthimis 2023-02-17 21:47:17 +00:00
test3.md Efthimis 2023-02-17 21:47:17 +00:00
test4.md Efthimis 2023-02-17 21:47:17 +00:00
test5.md Hopefully last image test 2023-02-17 21:49:57 +00:00
test6.md Hopefully last image test 2023-02-17 21:49:57 +00:00
test7.md Inline test2 2023-02-18 22:15:30 +00:00
test8.md test 2 2023-03-21 12:27:07 +00:00
test22.md aaa 2023-05-16 14:05:06 +01:00
test.md edits 2023-11-07 14:23:36 +00:00

README.md

9086 logo

A CPU that aims to be binary compatible with the 8086 and with as many optimisations as possible

Progress

  • 8086
    • Executing code
    • Is Turing complete
    • Can boot up MS-DOS / FreeDOS
    • Is completely binary compatible
    • Is pipelined
    • Is Out of Order
    • Is superscalar
    • Has been successfully synthesized

Simulating it

Both Verilator and Icarus Verilog can be used for simulation. You can select which one you want with the SIM variable on common.mk Specifically this list shows the software needed and the versions used during development (other versions should work as well)

  • Icarus Verilog : version 11.0 OR (preferred) Verilator : 5.006
  • bin86 : 0.16.21
  • GNU Make : 4.4.1
  • xxd : 2022-01-14
  • POSIX coreutils : GNU coreutils 9.1

After that you can run make on the top level directory and it should build everything and start the simulation

High level design overview

9086 logo

License

All parts of this project are licensed under the GNU General Public License version 3 or later

Versions

The version consist of three numbers:

  1. The CPU that this version aims to be compatible with
  2. The specific milestone
  3. Patch level

For example v1.3.2 aims to support 80186 code, is on the third milestone and has 2 bug fixes since the milestone was reached. haha