-
Notifications
You must be signed in to change notification settings - Fork 615
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Change in behavior between 3.3.2 and 3.4.0-RC3 for naming #1603
Comments
An example of what I suspect is the same issue happens in rocket-chip here: https://github.com/chipsalliance/rocket-chip/blob/c6b41bf5918bbafc7dccee70e208352e029d9505/src/main/scala/devices/debug/Periphery.scala#L112 Simple example of the bug: https://scastie.scala-lang.org/A2AN5lgAQHaRfWDFbOoyjQ Example of a workaround: https://scastie.scala-lang.org/UQoz4TceRxCFQIWZx8S37A |
This issue stems from the behavior of Basically, ports have special behavior where the first seed wins. The "first seed wins" is nice because it fixes #1352. It's not really clear how we both fix this issue and #1352. |
* WIP Commit * Add EdgeDataDiGraph with views to amortize graph construction * WIP, got basic structure, need tests to pipeclean * First tests pass. Need more. * Tests pass, more need to be written * More tests pass! Things should work, except for memories * Added clearPrev to fix digraph uses where caching prev breaks * Removed old Component. Documented IRLookup * Added comments. Make prev arg to getEdges * WIP: Refactoring for CircuitGraph * Refactored into CircuitGraph. Can do topological module analysis * Removed old versions * Added support for memories * Added cached test * More stufffff * Added implicit caching of connectivity * Added tests for IRLookup, and others * Many major changes. Replaced CircuitGraph as ConnectionGraph Added CircuitGraph to be top-level user-facing object ConnectionGraph now automatically shortcuts getEdges ConnectionGraph overwrites BFS as PriorityBFS Added leafModule to Target Added lookup by kind to IRLookup Added more tests * Reordered stuff in ConnectionGraph * Made path work with deep hierarchies. Added PML for IllegalClockCrossings * Made pathsInDAG work with current shortcut semantics * Bugfix: check pathless targets when shortcutting paths * Added documentation/licenses * Removed UnnamedToken and related functionality * Added documentation of ConnectionGraph * Added back topo, needed for correct solving of intermediate modules * Bugfix. Cache intermediate clockSources from same BFS with same root, but not BFS with different root * Added literal/invalid clock source, and unknown top for getclocksource * Bugfix for clocks in bundles * Add CompleteTargetSerializer and test * remove ClockFinder, be able to compile. * test is able to compile, but need to fix. * public and abstract DiGraph, remove DiGraphLike. * revert some DiGraph code, ConnectionGraphSpec passed. * CircuitGraphSpec passed. * minimize diff between master * codes clean up * override linearize and revert DiGraph * keep DiGraph unchanged. * make ci happy again. * codes clean up. * bug fix for rebase * remove wir * make scaladoc happy again. * update for review. * add some documentation. * remove tag * wip IRLookup * code clean up and add some doucmentations. * IRLookup cache with ModuleTarget guarded. * make unidoc and 2.13 happy Co-authored-by: Adam Izraelevitz <azidar@gmail.com> Co-authored-by: Albert Magyar <albert.magyar@gmail.com> Co-authored-by: Jack Koenig <koenig@sifive.com>
Type of issue: bug report
Impact: naming behavior change (back to old behavior)
Development Phase: request
Other information
If the current behavior is a bug, please provide the steps to reproduce the problem:
Given a somewhat weird (but useful) pattern:
The type of
val out
isSeq[Option[UInt]]
, this is actually very useful because the inner option allows us to skip indices in the namespace when there areNone
s:What is the current behavior?
In Chisel v3.4.0-RC3, this gives:
What is the expected behavior?
In Chisel v3.3.2, this gives:
What is the use case for changing the behavior?
Restore previous (useful) naming behavior
The text was updated successfully, but these errors were encountered: