Bug in segment layer reduction causing METAL2 to go in METAL1 (RISC-V).
* Bug: In Anabatic::AutoSegment::reduceDoglegLayer(), we did not check that not only source and target depth span was zero, but also both on the same one. This was seen in the RISC-V where a METAL2 small segment was demoted into METAL1 causing a gap in the routing (and a short in the underlying standart cell).
This commit is contained in:
parent
91f973c00f
commit
014dbe1bcc
|
@ -2030,7 +2030,7 @@ namespace Anabatic {
|
||||||
|
|
||||||
if ( (minSourceDepth == maxSourceDepth)
|
if ( (minSourceDepth == maxSourceDepth)
|
||||||
and (minTargetDepth == maxTargetDepth)
|
and (minTargetDepth == maxTargetDepth)
|
||||||
and (minTargetDepth == minTargetDepth) ) {
|
and (minSourceDepth == minTargetDepth) ) {
|
||||||
const Layer* layer = Session::getRoutingLayer(minSourceDepth);
|
const Layer* layer = Session::getRoutingLayer(minSourceDepth);
|
||||||
DbU::Unit side = Session::getWireWidth (minSourceDepth);
|
DbU::Unit side = Session::getWireWidth (minSourceDepth);
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue