Skip to content
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

Global router fails if there are too many ports on the floorplan #22

Open
oharboe opened this issue Aug 6, 2019 · 4 comments
Open

Global router fails if there are too many ports on the floorplan #22

oharboe opened this issue Aug 6, 2019 · 4 comments

Comments

@oharboe
Copy link
Contributor

oharboe commented Aug 6, 2019

I'm currently experiencing a crash with alpha-release in FRlefdef, but I don't know how to debug it:

  1. The FRlefdef included the alpha-release Docker image contains no debug information, nor is the source included.
  2. Trivial modules work, it's impractical without a deep understanding of the system how to reduce this to a small example
  3. The output from FRlefdef is uninformative, see below.
  4. What I'm testing OpenROAD on is proprietary, so at best I could provide an obfuscated somewhat scaled down version.
# FRlefdef --no-gui --script ./objects/nangate45/LEArrayScanChain/fastroute.rsyn
[deleted]
LV routing round 2, enlarge 20 
1 threshold, 20 expand
total Usage   : 2368335
Max H Overflow: 23
Max V Overflow: 2887
Max Overflow  : 2887
Num Overflow e: 6277
H   Overflow  : 3494
V   Overflow  : 231494
Final Overflow: 234988

LV Time: 3.870000 sec
updateType 1
iteration 1, enlarge 9, costheight 34, threshold 0 via cost 0 
log_coef 0.223050, healingTrigger 0 cost_step 30 L 0 cost_type 1 updatetype 1
initial grid wrong y1 x1 [0 0] , net start [10 0] routelen 305
 checking failed 0
Segmentation fault (core dumped)

@oharboe
Copy link
Contributor Author

oharboe commented Aug 8, 2019

After investigation, the above problem is due to the design having thousands of top-level pins. The particular bug in FRlefdef is not relevant to this bug-report.

The problem is that upon failure, the logs should have some helpful output to create a bug-report.

Ideally:

  • a clear error message
  • stack-trace

@tajayi
Copy link
Contributor

tajayi commented Aug 8, 2019

Out of cuiousity, did ioPlacer generate any warnings or errors?

@oharboe
Copy link
Contributor Author

oharboe commented Aug 8, 2019 via email

@tajayi
Copy link
Contributor

tajayi commented Aug 9, 2019

I'd say as much as you an share is welcome. Errror messages, logs, desings, etc.
Was mostly curious for filing an issue to the ioPlacer team to tell them what it does vs what it should be doing.

Ps. Also renaming the ticket

@tajayi tajayi changed the title Improve debugabilitiy of alpha-release Global router fails if there are too many ports on the floorplan Aug 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants