-
Notifications
You must be signed in to change notification settings - Fork 566
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
Rework top level buffer insertion (bufferinput/bufferoutput) in Resizer.cc #6250
base: master
Are you sure you want to change the base?
Rework top level buffer insertion (bufferinput/bufferoutput) in Resizer.cc #6250
Conversation
…for gcd up to cts Signed-off-by: andyfox-rushc <andy@rushc.com>
Signed-off-by: andyfox-rushc <andy@rushc.com>
…eparation of construction of moditerm/modbterm Signed-off-by: andyfox-rushc <andy@rushc.com>
Signed-off-by: andyfox-rushc <andy@rushc.com>
Signed-off-by: andyfox-rushc <andy@rushc.com>
clang-tidy review says "All clean, LGTM! 👍" |
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.
@andyfox-rushc , why does QoR change here?
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.
I believe because of the name change of the net. I will be digging into that to try to avoid the net name change, but it seems very strange to me that the timing result should be sensitive to net name changes.
If one looks at the defs (eg compare buffer_ports1.defok with master and pull request) the diffs are just some net names:
63,65c63,65
< - net1 ( input1 Z ) ( r1 D ) + USE SIGNAL ;
< - net2 ( input2 Z ) ( r2 D ) + USE SIGNAL ;
< - net3 ( output3 A ) ( r3 Q ) + USE SIGNAL ;
- net2 ( input1 Z ) ( r1 D ) + USE SIGNAL ; - net4 ( input2 Z ) ( r2 D ) + USE SIGNAL ; - net6 ( output3 A ) ( r3 Q ) + USE SIGNAL ;
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.
Its possible someone is hashing or comparing names. Sta itself shouldn't care about names unless it causes an SDC mismatch
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.
Sorry for the distraction, I will dig into this one and resolve. I realize the issue is with test buffer_ports4.tcl. buffer_ports1.tcl is fine.
Signed-off-by: andyfox-rushc <andy@rushc.com>
clang-tidy review says "All clean, LGTM! 👍" |
I am OK with the code change. The QoR change seems odd.
Cho
…On Wed, Nov 27, 2024 at 11:40 AM Matt Liberty ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
On src/rsz/test/buffer_ports4.ok
<#6250 (comment)>
:
Its possible someone is hashing or comparing names. Sta itself shouldn't
care about names unless it causes an SDC mismatch
—
Reply to this email directly, view it on GitHub
<#6250 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBVEJRUU6BEJWWYBG2X7CR32CYN35AVCNFSM6AAAAABSRV6D2WVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINRVHAZTSMZZG4>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
(1) Rewrite of the top level port buffering to handle modnet case.
(2) Fix for a latent bug in the bus port member iterator (which was causing the verilog writer to crash -- I am now writing out verilog on each stage of the flow).