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

Related to vector lanes in Gem5 for RISC-V Vector #23

Open
soniab opened this issue Nov 17, 2022 · 2 comments
Open

Related to vector lanes in Gem5 for RISC-V Vector #23

soniab opened this issue Nov 17, 2022 · 2 comments

Comments

@soniab
Copy link

soniab commented Nov 17, 2022

How many vector lanes does this Gem5 for RISC-V Vector support? Is it possible to change vector lanes at this point?

@huxuan0307
Copy link
Contributor

Our implementation uses register renaming instead of vector lanes. If you want to limit the number of vector execution units, you can modify the code of the O3CPU.

@soniab
Copy link
Author

soniab commented Nov 25, 2022

Thank you for clarifying this. I am using RISC-V MinorCPU, so it will be the same for in-order CPUs too. I have checked "BaseMinorCPU.py" and have observed that only one vector unit (MinorDefaultVecFU) is being used here. If I want to change the number of vector execution units then will it be enough to add the vector units here? Do I need to change some other files too?

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