You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
Recently, I tried to build a medium boom for performance test. It takes 80+ minutes for firrtl to generated the verilog source code. I also built it from this boom-template from scratch without local modification, and ended up with similar results.
The I found that firrtl complie time is related to the size of Load Queue. Following table lists my results:
Load queue entries: Total FIRRTL Compile Time
12: 126s
13: 187s
14: 387s
15: ???
16: 80+ minites
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Recently, I tried to build a medium boom for performance test. It takes 80+ minutes for firrtl to generated the verilog source code. I also built it from this boom-template from scratch without local modification, and ended up with similar results.
The I found that firrtl complie time is related to the size of Load Queue. Following table lists my results:
Load queue entries: Total FIRRTL Compile Time
The text was updated successfully, but these errors were encountered: