-
Notifications
You must be signed in to change notification settings - Fork 50
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
New option "--no-check-comb-loops" doesn't work with PeekPokeTester (possibly others) #155
Comments
@stevenmburns I have some PR's out to fix this, it will probably take a few days to get them reviewed and merged. Do you have a more filled out example of a test that illustrates the behavior of these circuits that contain apparent loops. When I put the circuit through to the interpreter, it was also flagged by the interpreters execution engine of having a loop. There's a command line flag that let's it continue on, but I'd like to see that it handles the circuit correctly when this flag is used. |
I have a firrtl pass to remove the combinational loop. Without this fix (or something like it) I can’t run it because the comb loop checker runs before my pass.
I can give you a circuit that should be simulate-able even though there are loops. I’ll gather that in a bit.
From: Chick Markley [mailto:notifications@github.com]
Sent: Friday, June 30, 2017 11:07 AM
To: freechipsproject/chisel-testers <chisel-testers@noreply.github.com>
Cc: Burns, Steven M <steven.m.burns@intel.com>; Mention <mention@noreply.github.com>
Subject: Re: [freechipsproject/chisel-testers] New option "--no-check-comb-loops" doesn't work with PeekPokeTester (possibly others) (#155)
@stevenmburns<https://github.com/stevenmburns> I have some PR's out to fix this, it will probably take a few days to get them reviewed and merged. Do you have a more filled out example of a test that illustrates the behavior of these circuits that contain apparent loops. When I put the circuit through to the interpreter, it was also flagged by the interpreters execution engine of having a loop. There's a command line flag that let's it continue on, but I'd like to see that it handles the circuit correctly when this flag is used.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#155 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABcUfjDzh5ox1RxlJbGbTbqyAsTDAb5mks5sJTlegaJpZM4N8728>.
|
The new option to "firrtl" isn't enabled in the testing flow.
This code still flags a combinational loop. (Does work from "firrtl" (command line) and the chisel3.Driver methods.)
Here is the error:
The text was updated successfully, but these errors were encountered: