diff options
| author | whitequark <whitequark@whitequark.org> | 2019-05-26 16:44:34 +0000 |
|---|---|---|
| committer | whitequark <whitequark@whitequark.org> | 2019-05-29 18:05:48 +0000 |
| commit | a0c9a70a5e6717aea37092720c899a463e482922 (patch) | |
| tree | b44884dec87a009ef9b0d4dc565dd596f785d408 /docs/generic.md | |
| parent | 68c16c2db78dec4af09da7bec5d386422d9264a1 (diff) | |
| download | nextpnr-a0c9a70a5e6717aea37092720c899a463e482922.tar.gz nextpnr-a0c9a70a5e6717aea37092720c899a463e482922.tar.bz2 nextpnr-a0c9a70a5e6717aea37092720c899a463e482922.zip | |
When choosing between labels for one net, always prefer ports.
1. Ports are already used in PCF and LPF files, so it is natural
that the developer would use them for constraints as well.
2. Unpredictable (the set of netlabels nextpnr looks at depends on
the optimizations during synthesis) net naming makes it impossible
for code generators like nMigen to reliably apply clock constraints.
Diffstat (limited to 'docs/generic.md')
0 files changed, 0 insertions, 0 deletions