- Notifications
You must be signed in to change notification settings - Fork0
A CDC8600 computer (4 CPUs, shared memory, SIMD) from scratch, to simulate and evaluate architectural design choices (pipelining, cache design, branch predictor, OoO execution, register renaming...). Simulate on 3 levels: 1. An execution-driven functional (ISA) simulator 2. An execution-driven timing model. 3. A trace-driven pipeline simulator.
tengjiang/CDC8600-from-scratch
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
This is the project repository for COMSE6998 in the Spring 2024 term,Computer Architecture Modeling, Simulation, and Evaluation.
Instructor: Jose Moreira, Columbia University
Create your own fork by using theFork button.In theCreate a new fork page, choose yourself as the owner (<owner>
) and a repository name (<project>
).You also want to check the box that saysCopy the main branch only and click on theCreate fork button.This will create your own private repo that you can edit at your heart's content.You will still need to checkout the repo into a working clone in your machine(s), and then commit changes from the working clone back to your private fork.You can create the working clone with:
git clonegit@github.com:
<owner>
/<project>
.git
You also need to set the original repository as theupstream repo:
cd
<project>
git remote add upstreamhttps://github.com/comse6998/spring2024.git
Once you have done this, the class repo is theupstream repo for your working clone, and your own fork is theorigin repo, as illustrated in this figure(see more detailshere):
Before starting any work of your own, you need to update your working clone with the changes that may have happened in the upstream repo.You can do that with:
git fetch upstream
git merge upstream/main main
After you have resolved all merge conflicts, you should commit and then push to your forked repo.Now both your working clone and your forked repo are updated from the upstream repo.When you are ready to move your contribution to the main repository, click theContribute button on your forked repo and ask for apull request.
Keep situational awareness!You should never make changes to the main repository.(If the configurations are right, you should not be able to.)But your private repo is yours!You can do anything you want, including deleting it and making a fresh fork.
About
A CDC8600 computer (4 CPUs, shared memory, SIMD) from scratch, to simulate and evaluate architectural design choices (pipelining, cache design, branch predictor, OoO execution, register renaming...). Simulate on 3 levels: 1. An execution-driven functional (ISA) simulator 2. An execution-driven timing model. 3. A trace-driven pipeline simulator.
Resources
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Releases
Packages0
Languages
- C++88.3%
- Fortran10.1%
- Makefile1.2%
- Shell0.4%