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
hierarchical compilation of designs for scalability #225
Comments
Original Redmine Comment From reading the webpage (annoying it's https without a certificate, but anyhow)
Anyhow, how large is your design? Very large (>>10M gates) designs can I would like to have Verilator generate such shells, but as with all things, time limits. |
Original Redmine Comment Thanks for your response For systemCass, the internal model can also be something different from system C. The test design we used was about 1.5M gates. For the test (I know this is a bad test...), we synthetised the vhdl (with synDc), and tried to simulated the generated structural verilog. With icarus verilog, it took about 18h to generate a binary. Today we are generating native verilog code that is much more compact. I don't fully understand how to use the system perl shells, and how they integrate with verilator. |
Original Redmine Comment Oh, you're simulating gates, not RTL? For that large a gatesim, you'll want a commercial simulator. That's not what Converting it to RTLish is interesting though... I'm surprised it goes that |
Original Redmine Comment Gate simulation is not our goal. This was just a test We now do output rtl level verilog. But it currently has interfaces with vhpi or vpi. Thanks |
Original Redmine Comment BTW, I suspect you already thought of this, but make sure your system isn't paging. |
#2182 is addressing this issue. |
Author Name: joe barjo
Original Redmine Issue: 225 from https://www.veripool.org
Original Date: 2010-03-17
Hi
Our tests show that verilator is unusable for rather big designs.
The reason for this (from what I understand) is that it doesn't support hierarchical compilation.
I don't know much about verilator internals, I think I have a suggestion to handle hierarchy with cycle based simulators.
SystemCass is a systemC "compatible" simulator which has a much better performance because the models are composed of 3 functions:
* Transition function;
* Moore generation function;
* Mealy generation function.
These 3 functions should be "easily" generated by verilator.
A hierarchical compilation not only brings scalability, but it should also ease parallelism for the code generation.
This feature would be an overkill.
More info at
https://www-asim.lip6.fr/trac/systemcass/
Thanks
The text was updated successfully, but these errors were encountered: