-
Notifications
You must be signed in to change notification settings - Fork 0
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
Questions about evaluator.cpp #12
Comments
@liangrj2014 Looking forward to your help |
Thanks for pointing out the issue! We will address it soon |
Could you please check whether adding "flag[zh][xl][yl] = net->idx()" below line 524 in the evaluator.cpp resolve this issue? Thanks in advance! |
Thanks! The added line works. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In
evaluator.cpp
, the functionNVR_DB::read_gr_solution
maintains a vectorflag
to record the routing guides of a net. The valid guides are categorized towire
andvia
types. And during reading guides,flag
can only be updated bywire
type guides and functionNVR_DB::update_nonstack_via_counter
.Here is my case:
Access Points of a pin:
[(3, 0, 396), (3, 1, 396)]
I try to meet the pin by point
(3, 0, 396)
by a via from layer2 (metal3) to layer3 (metal4), and my guide is0 396 2 0 396 3
.The only entrance to set
flag
is in functionNVR_DB::update_nonstack_via_counter
, whereflag[2][0][396]
is set. Since nowire
type guide is passing through the point(3, 0, 396)
and no via starts from point(3, 0, 396)
, the variableflag[3][0][396]
is not set and my guide for this net is judged to be open byevaluator.cpp
.My question is:
Is it admissable to link the pin access point by a via like this? Or does the evaluator.cpp miss such case?
Looking forward to your help!
The text was updated successfully, but these errors were encountered: