Repository navigation
Conversation
There was a problem hiding this comment.
Code Review
This pull request introduces a new LEF technology file, asap7_tech_1x_260907.lef, for the ASAP7 platform. The review feedback identifies a minor issue where the TYPE ROUTING ; and DIRECTION VERTICAL ; statements are duplicated within the LAYER M7 block, which should be cleaned up to prevent parser warnings.
| TYPE ROUTING ; | ||
| DIRECTION VERTICAL ; |
There was a problem hiding this comment.
Signed-off-by: LeeJaKang <wkrkd95@postech.ac.kr>
4792394 to
db813d4
Compare
🔍 QoR checkMetrics reflect the PR merge build — i.e. what will land on the target branch. Commit 62 design(s) checked — 0 with regression(s), 0 without a comparable baseline. |
|
I've assumed that the LEF58_RIGHTWAYONGRIDONLY & LEF58_RECTONLY were representing double patterning. If you remove them then you should add a MASK statement if they are such. Please clarify. |
|
Yes, that is correct. Those rules were added due to multi-patterning. https://www.sciencedirect.com/science/article/pii/S002626921630026X I have also attached the image below for reference.
|
|
Thanks. This PR doesn't actually switch to using the new tech but we can take that up in another PR. |
fbc8fa4
into
The-OpenROAD-Project:master
Signed-off-by: Matt Liberty <mliberty@precisioninno.com>


Summary
This adds a new file,
flow/platforms/asap7/lef/asap7_tech_1x_260907.lef. It is the same asasap7_tech_1x_201209.lef, but with fixes to layers M1, M2, and M3. The fixes makethese layers match the ASAP7 Design Rule Manual
and the original ASAP7 paper. This PR only adds a new file. It does not change the old
file. So nothing that uses
asap7_tech_1x_201209.lefwill break.What changed (only layers M1-M3, layers M4-M9 are the same)
AREA 0.000666->AREA 0.000504um^2. MatchesM1.A.1 / M2.A.1 / M3.A.1.
LEF58_SPACING ... WITHIN 0.02->WITHIN 0. WithWITHIN 0.02on, cases that should be checked as corner-to-corner (M2.S.6) wereinstead checked as tip-to-tip (M2.S.4).
LEF58_WIDTHTABLE(
WIDTHTABLE 0.018 0.09 0.162 0.234 0.306 0.378). This rule only exists for M4-M7(M4.W.3 / M4.W.4).
LEF58_RIGHTWAYONGRIDONLY. M4.AUX.2 is M4-M7 only.LEF58_RECTONLY. M4.AUX.3("may not bend") is M4-M7 only.
CORNERSPACING CONVEXCORNER WIDTH 0.0 SPACING 0.02-> adds
CORNERONLY 0.02. Matches M2.S.6, corner-to-corner spacing >= 20 nm.Related pull request
The same content is also included in The-OpenROAD-Project/asap7sc7p5t_28#9.