Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

split branch prediction CPU into its own file #61

Closed
powerjg opened this issue May 20, 2019 · 0 comments · Fixed by #74
Closed

split branch prediction CPU into its own file #61

powerjg opened this issue May 20, 2019 · 0 comments · Fixed by #74

Comments

@powerjg
Copy link
Contributor

powerjg commented May 20, 2019

It would be better to have a separate file for the branch predictor CPU data path than replacing the simple pipelined CPU data path. It's a little unfortunate to have lots of code duplication, but, overall, I think it's better to split this out on its own.

I foresee having many different pipeline designs in the pipelined/ directory:

  • cpu-simple.scala: Base pipelined design (e.g., answer to lab3)
  • cpu-bp.scala: Pipelined design with a branch predictor
  • cpu-seqmem.scala: Pipelined design with sequential instead of asynchronous memory.
  • Others????
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant