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

Cannot compile muir-sim #1

Open
RazvanN7 opened this issue Feb 26, 2020 · 2 comments
Open

Cannot compile muir-sim #1

RazvanN7 opened this issue Feb 26, 2020 · 2 comments

Comments

@RazvanN7
Copy link

RazvanN7 commented Feb 26, 2020

When running the command:

make chisel NPROCS=4 NUM_PTRS=2 NUM_VALS=1 NUM_RETS=0

I get the following error:
Screenshot from 2020-02-26 14-12-42

Which I was able to fix by modifying hardware/chisel/dandelion/src/main/scala/node/Alu and replacing Floor with RoundDown. I didn't make a PR as I do not have the dandelion repo which is a git submodule of muIR-sim. This made the advanced the compilation to the point where I get:

Screenshot from 2020-02-26 14-17-14

This I don't know how to bypass.

@amsharifian
Copy link
Member

amsharifian commented Feb 26, 2020

Hi Razvan,
The first problem is probably because of the version difference in dsptools library. It seems there is an update for dsptools and they have replaced Floor with RoundDown. I updated the interface.

For the second problem, if you look at this file: muir-sim/hardware/chisel/src/test/scala/accel/VCRAccel.scala this is where we instantiate the accelerators. What you need to do is make sure your accelerator class in line: 73 is exactly what you intend to build, in DandelionSimAccelMain class. Moreover, you have to make sure the values for NUM_PTRS, NUM_VALS and NUM_RETS matches with the accelerated function. For instance, in the case of test01, we have 0 pointers, 2 values and 1 returns. So you have to make sure these values are properly set at the build time.

I'm working on a run.py file which accepts a JSON as configure file and it automatically takes care of setting these parameters for building a new accelerator. Because currently, it's very error-prone to always make sure these variables are properly set according to the actual accelerator.

@amsharifian
Copy link
Member

The README doc is misleading, I updated the text, but still needs more details...

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

No branches or pull requests

2 participants