-
Notifications
You must be signed in to change notification settings - Fork 174
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
Fix chiplets bus #1664
Fix chiplets bus #1664
Conversation
4612598
to
b60b521
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thank you for adding the bus debugger !
Btw, I like the rstest
effect on the tests too.
processor/src/debug.rs
Outdated
fn source(&self) -> &str; | ||
} | ||
|
||
/// Note: we use `Vec` internall instead of a `BTreeMap` as a workaround for field elements not |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: internally
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thank you! This is a great addition and I really like the concept of bus messages. I left a few comments inline with potential improvement suggestions.
Also, just to double check: does this have any noticeable impact on the performance of the auxiliary trace building step?
24a7e65
to
9fda218
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Thank you! I left a few small comments inline - but this is basically good to go.
Closes: #1545
Our bus is quite hard to debug due to the lack of insight into which request/response were not matched when things go wrong. This PR
miden-base
node_index
in themrupdate
andmpverify
tests. There were some tests failing inmiden-base
due to that, but I think it was a bug I introduced in the refactoring (which wasn't caught by our tests).Some tests in
miden-base
still fail, but only due to a problem with rcombbase. Since it is going away with #1661, I didn't spend time debugging/fixing it - we should do that with #1661 (if there is still a problem).Fun fact: with the new
BusDebugger
, identifying the problems with the bus was very quick 😄