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

Jump to bottom

Large structures expose GCC/clang compile time bug #1248

Closed
veripoolbot opened this issue Dec 7, 2017 · 3 comments
Closed

Large structures expose GCC/clang compile time bug #1248

veripoolbot opened this issue Dec 7, 2017 · 3 comments
Assignees
@wsnyder
Labels
area: performance Issue involves performance issues resolution: fixed Closed; fixed

Comments

@veripoolbot
Copy link
Contributor

Author Name: Wilson Snyder (@wsnyder)
Original Redmine Issue: 1248 from https://www.veripool.org

Original Assignee: Wilson Snyder (@wsnyder)

Very large models cause Verilator to generate classes with a large number of member variables. When these are compiled with GCC or clang (LLVM), these appear to expose a O(n^2) slowdown.

I have filed a GCC bug related to this:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83309

This appears to apply to all current versions of GCC and clang.

As it will be a long time before this is resolved a Verilator workaround is desired.
@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2017-12-09T17:03:14Z

Matching problem in clang/LLVM:

https://bugs.llvm.org/show_bug.cgi?id=35585

@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2017-12-09T17:03:48Z

Workaround added to Verilator in git towards 3.917.

@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2018-01-02T23:14:46Z

In 3.918.

@veripoolbot veripoolbot added area: performance Issue involves performance issues resolution: fixed Closed; fixed labels Dec 22, 2019
@wsnyder wsnyder mentioned this issue May 3, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wsnyder wsnyder

Labels
area: performance Issue involves performance issues resolution: fixed Closed; fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wsnyder @veripoolbot