Skip to content

Commit ca29f38

Browse files
eder-matheuseder-matheus
committed
ppl: update unit tests
Signed-off-by: Eder Monteiro <emrmonteiro@precisioninno.com>
1 parent e3cab82 commit ca29f38

8 files changed

+562
-1124
lines changed

‎src/ppl/test/write_pin_placement1.ok‎

Lines changed: 0 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -14,59 +14,5 @@ Found 0 macro blocks.
1414
[INFO PPL-0004] Number of I/O w/o sink 0
1515
[INFO PPL-0006] Number of I/O Groups 2
1616
[INFO PPL-0012] I/O nets HPWL: 4475.54 um.
17-
[INFO PPL-0070] Pin clk placed at (42.27um, 0.04um) instead of (42.27um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
18-
[INFO PPL-0070] Pin req_msg[31] placed at (59.76um, 0.04um) instead of (59.76um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
19-
[INFO PPL-0070] Pin req_msg[30] placed at (59.38um, 0.04um) instead of (59.38um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
20-
[INFO PPL-0070] Pin req_msg[29] placed at (58.99um, 0.04um) instead of (58.99um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
21-
[INFO PPL-0070] Pin req_msg[28] placed at (58.62um, 0.04um) instead of (58.62um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
22-
[INFO PPL-0070] Pin req_msg[27] placed at (58.23um, 0.04um) instead of (58.23um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
23-
[INFO PPL-0070] Pin req_msg[26] placed at (57.85um, 0.04um) instead of (57.85um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
24-
[INFO PPL-0070] Pin req_msg[25] placed at (57.48um, 0.04um) instead of (57.48um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
25-
[INFO PPL-0070] Pin req_msg[24] placed at (57.09um, 0.04um) instead of (57.09um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
26-
[INFO PPL-0070] Pin req_msg[23] placed at (56.72um, 0.04um) instead of (56.72um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
27-
[INFO PPL-0070] Pin req_msg[22] placed at (56.34um, 0.04um) instead of (56.34um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
28-
[INFO PPL-0070] Pin req_msg[21] placed at (55.95um, 0.04um) instead of (55.95um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
29-
[INFO PPL-0070] Pin req_msg[20] placed at (55.58um, 0.04um) instead of (55.58um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
30-
[INFO PPL-0070] Pin req_msg[19] placed at (55.20um, 0.04um) instead of (55.20um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
31-
[INFO PPL-0070] Pin req_msg[18] placed at (54.81um, 0.04um) instead of (54.81um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
32-
[INFO PPL-0070] Pin req_msg[17] placed at (54.44um, 0.04um) instead of (54.44um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
33-
[INFO PPL-0070] Pin req_msg[16] placed at (54.05um, 0.04um) instead of (54.05um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
34-
[INFO PPL-0070] Pin req_msg[15] placed at (53.67um, 0.04um) instead of (53.67um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
35-
[INFO PPL-0070] Pin req_msg[14] placed at (53.30um, 0.04um) instead of (53.30um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
36-
[INFO PPL-0070] Pin req_msg[13] placed at (52.91um, 0.04um) instead of (52.91um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
37-
[INFO PPL-0070] Pin req_msg[12] placed at (52.53um, 0.04um) instead of (52.53um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
38-
[INFO PPL-0070] Pin req_msg[11] placed at (52.16um, 0.04um) instead of (52.16um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
39-
[INFO PPL-0070] Pin req_msg[10] placed at (51.77um, 0.04um) instead of (51.77um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
40-
[INFO PPL-0070] Pin req_msg[9] placed at (51.40um, 0.04um) instead of (51.40um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
41-
[INFO PPL-0070] Pin req_msg[8] placed at (51.02um, 0.04um) instead of (51.02um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
42-
[INFO PPL-0070] Pin req_msg[7] placed at (50.63um, 0.04um) instead of (50.63um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
43-
[INFO PPL-0070] Pin req_msg[6] placed at (50.26um, 0.04um) instead of (50.26um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
44-
[INFO PPL-0070] Pin req_msg[5] placed at (49.88um, 0.04um) instead of (49.88um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
45-
[INFO PPL-0070] Pin req_msg[4] placed at (49.49um, 0.04um) instead of (49.49um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
46-
[INFO PPL-0070] Pin req_msg[3] placed at (49.12um, 0.04um) instead of (49.12um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
47-
[INFO PPL-0070] Pin req_msg[2] placed at (48.73um, 0.04um) instead of (48.73um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
48-
[INFO PPL-0070] Pin req_msg[1] placed at (48.35um, 0.04um) instead of (48.35um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
49-
[INFO PPL-0070] Pin req_msg[0] placed at (47.98um, 0.04um) instead of (47.98um, 0.00um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
50-
[INFO PPL-0070] Pin resp_val placed at (100.09um, 26.95um) instead of (100.13um, 26.95um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
51-
[INFO PPL-0070] Pin req_val placed at (84.45um, 100.77um) instead of (84.45um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
52-
[INFO PPL-0070] Pin resp_msg[15] placed at (26.32um, 100.77um) instead of (26.32um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
53-
[INFO PPL-0070] Pin resp_msg[14] placed at (25.93um, 100.77um) instead of (25.93um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
54-
[INFO PPL-0070] Pin resp_msg[13] placed at (25.55um, 100.77um) instead of (25.55um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
55-
[INFO PPL-0070] Pin resp_msg[12] placed at (25.18um, 100.77um) instead of (25.18um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
56-
[INFO PPL-0070] Pin resp_msg[11] placed at (24.80um, 100.77um) instead of (24.80um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
57-
[INFO PPL-0070] Pin resp_msg[10] placed at (24.41um, 100.77um) instead of (24.41um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
58-
[INFO PPL-0070] Pin resp_msg[9] placed at (24.04um, 100.77um) instead of (24.04um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
59-
[INFO PPL-0070] Pin resp_msg[8] placed at (23.66um, 100.77um) instead of (23.66um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
60-
[INFO PPL-0070] Pin resp_msg[7] placed at (23.27um, 100.77um) instead of (23.27um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
61-
[INFO PPL-0070] Pin resp_msg[6] placed at (22.89um, 100.77um) instead of (22.89um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
62-
[INFO PPL-0070] Pin resp_msg[5] placed at (22.52um, 100.77um) instead of (22.52um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
63-
[INFO PPL-0070] Pin resp_msg[4] placed at (22.14um, 100.77um) instead of (22.14um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
64-
[INFO PPL-0070] Pin resp_msg[3] placed at (21.75um, 100.77um) instead of (21.75um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
65-
[INFO PPL-0070] Pin resp_msg[2] placed at (21.38um, 100.77um) instead of (21.38um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
66-
[INFO PPL-0070] Pin resp_msg[1] placed at (21.00um, 100.77um) instead of (21.00um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
67-
[INFO PPL-0070] Pin resp_msg[0] placed at (20.61um, 100.77um) instead of (20.61um, 100.80um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
68-
[INFO PPL-0070] Pin req_rdy placed at (0.04um, 11.83um) instead of (0.00um, 11.83um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
69-
[INFO PPL-0070] Pin reset placed at (0.04um, 52.99um) instead of (0.00um, 52.99um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
70-
[INFO PPL-0070] Pin resp_rdy placed at (0.04um, 88.69um) instead of (0.00um, 88.69um). Pin was snapped to a routing track, to the manufacturing grid or moved away from blocked region.
7117
No differences found.
7218
No differences found.

0 commit comments

Comments
 (0)