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

[FIRRTL][CheckCombLoops] don't crash on force+rwprobeop, workaround. #6821

Merged

Conversation

dtzSiFive
Copy link
Contributor

Unbreak this, at cost of missing loops through force, while the better fix is being worked out.

cc #6820.

Unbreak this, at cost of missing loops through force, while
the better fix is being worked out.

cc llvm#6820.
@dtzSiFive dtzSiFive added the FIRRTL Involving the `firrtl` dialect label Mar 13, 2024
Copy link
Contributor

@prithayan prithayan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine as a temporary fix, I am working on handling this case.

@dtzSiFive
Copy link
Contributor Author

Thank you!

@dtzSiFive dtzSiFive merged commit fea328a into llvm:main Mar 13, 2024
4 checks passed
@dtzSiFive dtzSiFive deleted the fix/check-comb-loops-rwprobe-workaround branch March 13, 2024 18:58
%0 = firrtl.asClock %c0_ui1 : (!firrtl.uint<1>) -> !firrtl.clock
firrtl.ref.force %clock, %c1_ui1, %clockProbe, %0 : !firrtl.clock, !firrtl.uint<1>, !firrtl.clock
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can the PR add an XFAIL test (would have to be another file) that is checking that a cycle involving a force is fixed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You got it, here: #6823 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FIRRTL Involving the `firrtl` dialect
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants