The top one is different from the others in that it is uni-directional and doesn't deal with long lines.
All the others are bi-directional and deal with long lines.
However, these are not the only bi-directional PIPs in an INT_L tile associated with long lines.
Thus, the problem would not seem to be long lines themselves, but rather these specific long lines.
What is unknown is whether these pips are actually solved for
or whether the problem is that the code that checks if they are disambiguated needs fixing.
Figuring this out could help complete the pip fuzzer
By iteration 135, the pip fuzzer has solved for all in an INT_L tile except for 8 PIPs.
The 8 unsolved pips are:
GFAN0->>BYP_ALT1 LV_L18<<->>LH0 LV_L0<<->>LH0 LVB_L0<<->>LVB_L12 LV_L18<<->>LH12 LV_L0<<->>LH12 LH0<<->>LH12 LV_L0<<->>LV_L18
The top one is different from the others in that it is uni-directional and doesn't deal with long lines.
All the others are bi-directional and deal with long lines. However, these are not the only bi-directional PIPs in an INT_L tile associated with long lines. Thus, the problem would not seem to be long lines themselves, but rather these specific long lines.
What is unknown is whether these pips are actually solved for
or whether the problem is that the code that checks if they are disambiguated needs fixing.
Figuring this out could help complete the pip fuzzer