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

fsm_detect takes a very long time #1634

Closed
Ravenslofty opened this issue Jan 14, 2020 · 1 comment · Fixed by #1637
Closed

fsm_detect takes a very long time #1634

Ravenslofty opened this issue Jan 14, 2020 · 1 comment · Fixed by #1637
Assignees

Comments

@Ravenslofty
Copy link
Collaborator

Ravenslofty commented Jan 14, 2020

Steps to reproduce the issue

Reproducible with 9fbeb57 - sorry I couldn't reduce the testcase any further, but bugpoint can't currently diagnose infinite loops.

Using infinite-loop.tar.gz, run yosys -p "synth_ecp5" infinite-loop.v.

Expected behavior

fsm_detect completes successfully.

Actual behavior

Yosys spends five and a half minutes at:

2.22. Executing FSM pass (extract and optimize FSM).

2.22.1. Executing FSM_DETECT pass (finding FSMs in design).

while using 100% CPU.

There isn't an FSM in my code, or at least not an intentional one, but fsm_detect is hanging on the design.

I'm not entirely sure who to ping on this, but I'll ping @cliffordwolf as she worked on this last.

@Ravenslofty Ravenslofty changed the title Infinite loop in fsm_detect fsm_detect takes a very long time Jan 14, 2020
@Ravenslofty
Copy link
Collaborator Author

This does terminate, but as Yosys itself reports: Time spent: 99% 1x fsm_detect (323 sec), 0% 8x techmap (0 sec), ...

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

Successfully merging a pull request may close this issue.

2 participants