riscv
/
coriolis
mirror of https://gitlab.lip6.fr/vlsi-eda/coriolis.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
coriolis/anabatic/src/NetBuilderVH.cpp

651 lines
24 KiB
C++
Raw Normal View History

In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
// -*- C++ -*-
//
// This file is part of the Coriolis Software.
Happy New Year 2018 ! Update license years...
2018-01-06 10:55:44 -06:00
// Copyright (c) UPMC 2018-2018, All Rights Reserved
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
//
// +-----------------------------------------------------------------+
// | C O R I O L I S |
// | A n a b a t i c - Routing Toolbox |
// | |
// | Author : Jean-Paul CHAPUT |
// | E-mail : Jean-Paul.Chaput@lip6.fr |
// | =============================================================== |
// | C++ Module : "./NetBuilderVH.cpp" |
// +-----------------------------------------------------------------+
#include <cstdlib>
#include <sstream>
#include "hurricane/Bug.h"
#include "hurricane/Breakpoint.h"
#include "hurricane/Error.h"
#include "hurricane/Warning.h"
#include "hurricane/DebugSession.h"
#include "hurricane/Layer.h"
#include "hurricane/BasicLayer.h"
#include "hurricane/RegularLayer.h"
#include "hurricane/Technology.h"
#include "hurricane/DataBase.h"
#include "hurricane/Net.h"
#include "hurricane/NetExternalComponents.h"
#include "hurricane/NetRoutingProperty.h"
#include "hurricane/RoutingPad.h"
#include "hurricane/RoutingPads.h"
#include "hurricane/Pad.h"
Pin management implemented for NetBuilderHV. * Bug: In Katana::Track::expandFreeInterval(), the OutsideElement case was not handled correctly, the end index must be increased in that case. As a result, this function was returning too short an interval. This was affecting the computation of perpandicular free interval in DataNegociate::update() for perpandicular fixed but not in a track. * New: In Anabatic::NetBuilder and NetBuilderVH, now manage GCells with one Pin, and up to three globals. Used to put terminals at the edge of a block. * New: In EtesianEngine, now manage placed Pins. (done through extractInstanceName()) * Change: In CRL::RoutingGauge::getHorizontalGauge() no longer skip PinOnly gauges to find the reference one (same goes for vertical).
2019-03-10 07:25:43 -05:00
#include "hurricane/Pin.h"
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
#include "hurricane/Plug.h"
#include "hurricane/Cell.h"
#include "hurricane/Instance.h"
#include "hurricane/Vertical.h"
#include "hurricane/Horizontal.h"
#include "crlcore/AllianceFramework.h"
#include "crlcore/RoutingGauge.h"
#include "crlcore/Measures.h"
#include "anabatic/AutoContactTerminal.h"
#include "anabatic/AutoContactTurn.h"
#include "anabatic/AutoContactHTee.h"
#include "anabatic/AutoContactVTee.h"
#include "anabatic/AutoSegment.h"
#include "anabatic/NetBuilderVH.h"
#include "anabatic/AnabaticEngine.h"
namespace Anabatic {
using std::swap;
using Hurricane::Transformation;
using Hurricane::Warning;
using Hurricane::Error;
Pin management implemented for NetBuilderHV. * Bug: In Katana::Track::expandFreeInterval(), the OutsideElement case was not handled correctly, the end index must be increased in that case. As a result, this function was returning too short an interval. This was affecting the computation of perpandicular free interval in DataNegociate::update() for perpandicular fixed but not in a track. * New: In Anabatic::NetBuilder and NetBuilderVH, now manage GCells with one Pin, and up to three globals. Used to put terminals at the edge of a block. * New: In EtesianEngine, now manage placed Pins. (done through extractInstanceName()) * Change: In CRL::RoutingGauge::getHorizontalGauge() no longer skip PinOnly gauges to find the reference one (same goes for vertical).
2019-03-10 07:25:43 -05:00
using Hurricane::Pin;
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
NetBuilderVH::NetBuilderVH ()
: NetBuilder()
{ }
NetBuilderVH::~NetBuilderVH () { }
Clean parameters for routing topologies. Improved 2RL- support. Previously, the relevant NetBuilder and routing strategies where directly guessed from the RoutingGauge traits. This is no longer doable as the combinations increases. Now to configure both the global and detailed router we need three "parameters" : 1. The routing gauge itself (tells which layers are in which directions) and how to make the VIAs. 2. The NetBuilder to use, they are identified by strings. Currently we support: * "HV,3RL+", for all SxLib derived standard cells. * "VH,2RL", for hybrid routing (over the cell, but terminals are also in the first RL). * "2RL-", for strict channel routing. * "VH,3RL+", an attempt for FreePDK 45, not optimized enough to be considered as usable. 3. The routing style, mostly affect the way the GCell grid will be built. * VH : first RL is V. * HV : first RL is H. * OTH : Run in full over-the-cell mode (needs at least 3RL). * Channel : Run in *strict* channel routing mode (no routing over the standard cells). * Hybrid : Create channels, but can use H tracks over the standard cells. Thoses three parameters are partly overlapping and must be sets in a consistent manner, otherwise strange results may occurs. * New: CRL::RoutingGauge::getFirstRoutingGauge(), to get the lowest layer available for routing (not a PinOnly, not a PowerSupply). * Change: In CRL::RoutingGauge::isHV() and isVH(), were previously always returning false when the gauge was 2RL only. Now, check on the first usable RL. * Bug: In cumulus/plugins.block.configuration._loadRoutingGauge(), there was a bad computation of the deep RLs when the top layer was not defined. Occured for 2RL gauges only. * Bug: In Anabatic::RpsInRow::slacken() (LayerAssign), forgotten curly braces in the test to skip METAL2 terminals. * Change: In Etestian::BloatChannel::getDx(), adjust the bloating policy to converge on Arlet6502. Always ensure that there is a 50% ratio between terminal used V-tracks and free ones. If there is more than 80% of terminals, add one more track. * Bug: In AnabaticEngine & KatanaEngine, KatanaEngine is a derived class of AnabaticEngine. They uses Anabatic::Configuration and Katana::Configuration that also derives from each other. I though I had made one configuration attribute in the base class that was using the right Configuration. But no. I did have two configurations attributes, one in AnabaticEngine and one in KatanaEngine, the later "shadowing" the former. As a results, parameters modified in AnabaticEngine, *after* the initial creation of the tool *where never seen* at Katana level (due to it's own duplicate). What a mess. Now there is only one attribute in the *base* class Anabatic, which is created through a new virtual function _createConfiguration() called in _postCreate() which allocate the right Configuration according to the dynamic type of the tool (KatanaEngine). In KatanaEngine, access the configuration through the attribute (_configuration) and not the accessor (getConfiguration()). * Bug: In KatanaEngine, no longer directly use the _configuration attribute (which is not accessible anyway) but the getConfiguration() accessor. The accessor perform a static_cast from the Super::getConfiguration() into Katana::Configuration. Complete cleanup of the various configuration accessors. * New: AnabaticEngine::setupNetBuilder(), perform an early check of the requested NetBuilderStyle. The NetBuilderStyle is just a string that will be matched against the (hard-coded) supported NetBuilders. Then check the topological characteristics against the capabilities of the gauge (HV, VH and so on). Still a bit too hard-coded for now. This function has been split from AnabaticEngine::_loadGrByNet(). * Change: AnabaticEngine::isChannelStyle() renamed from isChannelMode(). * New: In Anabatic::Configuration, two new attributes to select the topology and routing style: - _netBuilderStyle to explicitely select the NetBuilder to use. It's a string, which is provided by each NetBuilder. - _routingStyle to define how the overall routing will work. It's a set of flags (StyleFlags): * VH : first RL is V. * HV : first RL is H. * OTH : Run in full over-the-cell mode (needs at least 3RL). * Channel : Run in *strict* channel routing mode (no routing over the standard cells). * Hybrid : Create channels, but can use H tracks over the standard cells. * New: In anabatic/Constants, add StyleFlags to define how the router should operate (see above). * Bug: In Anabatic::GCell, in CTOR, no reason to set up the HChannelGCell flag. * Bug: In Anabatic::GCell::updateDensity(), when computing layers non contiguous saturation, do not systematically skip RL 0, but only if it's PinOnly. * Change: In Anabatic::NetBuilder, rename isTwoMetal by isStrictChannel. * Change: In Anabatic::NetBuilderHV, rename doRp_AccessNorthPin() in doRp_AccessNorthSouthPin(). More accurate. * Bug: In NetBuilderHV::_do_1G_xM1_1PinM2(), the wires to connect the M1 terminals where created *twice*. Uterly stupid, there where placed in overlap by the router! * New: In AnabaticEngine, new accessors to the NetBuilderStyle and RoutingStyle, proxies towards Configuration. * Bug: In Manipulator::relax(), if there are two doglegs to be done, but they are in the same GCell, only do one (the conflicting interval) is short. * Change: In Katana::Session, rename isChannelMode() into isChannelStyle(). * Change: In TrackSegment::isUnbreakable() and isStrap(), return false when the base segment is a *weak global* (aligned with a global one). * Change: In Katana::Row::createChannel(), correctly distinguish between *strict channel* style and *hybrid* style. Tag the GCells as std cells row or channels only in the former case.
2022-11-26 06:07:12 -06:00
string NetBuilderVH::getStyle ()
{ return "VH,3RL+"; }
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
void NetBuilderVH::doRp_AutoContacts ( GCell* gcell
, Component* rp
, AutoContact*& source
, AutoContact*& target
, uint64_t flags
)
{
cdebug_log(145,1) << getTypeName() << "::doRp_AutoContacts()" << endl;
cdebug_log(145,0) << rp << endl;
source = target = NULL;
Point sourcePosition;
Point targetPosition;
const Layer* rpLayer = rp->getLayer();
size_t rpDepth = Session::getLayerDepth( rp->getLayer() );
Flags direction = Session::getDirection ( rpDepth );
DbU::Unit viaSide = Session::getViaWidth ( rpDepth );
getPositions( rp, sourcePosition, targetPosition );
if (sourcePosition.getX() > targetPosition.getX()) swap( sourcePosition, targetPosition );
if (sourcePosition.getY() > targetPosition.getY()) swap( sourcePosition, targetPosition );
GCell* sourceGCell = Session::getAnabatic()->getGCellUnder( sourcePosition );
GCell* targetGCell = Session::getAnabatic()->getGCellUnder( targetPosition );
if (rpDepth == 0) {
rpLayer = Session::getContactLayer(0);
direction = Flags::Vertical;
viaSide = Session::getViaWidth( rpDepth );
RoutingPad* rrp = dynamic_cast<RoutingPad*>( rp );
if (rrp) {
// if (not getAnabatic()->getConfiguration()->selectRpComponent(rrp)) {
// cerr << Warning( "%s::doRp_AutoContacts(): %s has no components on grid."
// , getTypeName().c_str()
// , getString(rp).c_str() ) << endl;
// }
} else {
cerr << Warning( "%s::doRp_AutoContacts(): %s is *not* a RoutingPad."
, getTypeName().c_str()
, getString(rp).c_str() ) << endl;
}
}
// Non-M1 terminal or punctual M1 protections.
Added direct management of macro blocks I/O pins in METAL2 & METAL3. The decoupling of the cell gauge and the routing gauge implies that the METAL2 & METAL3 terminals of macro blocks cannot be aligned on the routing tracks anymore. That is, an horizontal METAL2 terminal will not be on a track axis, but offgrid, so we no longer can use a METAL2 horizontal segment to connect to it. Making an adjustement between the offgrid terminal and the on-grid segment has proven too complex and generating difficult configuration for the router. Moreover, METLA2 terminal could be fully inside a METAL2 blockage. So now, when the gauges are decoupled, we connect the METAL2 and METAL3 the same way we do for METAL1: *from above* in the perpandicular direction and using a *sliding* VIA. We assume that those kind of terminals in upper metals are quite long. * New: In Hurricane::Rectilinear, export the isNonRectangle() method to the Python interface. * New: In CRL::RoutingGauge, add function isSuperPitched() with the associated boolean attribute. Set to true when each pitch of each layer is independant (not low fractional multiples). * New: In AnabaticEngine, add the ability to temporarily disable the canonize() operation (mainly used in dogleg creation). * New: In AutoSegment::canonize(), do nothing if the operation is disabled by AnabaticEngine. * Bug: In Session::_revalidateTopology(), disable the canonization during the topology updating of a net. Too early canonization was occuring in makeDogleg() leading to incoherencies when performing the later canonization stage over the complete net. Mostly occured in the initial build stage of the net. * New: In GCell, add function postGlobalAnnotate(), if a layer is fully blocked (above 0.9), typically, under a blockage, add a further capacity decrease of 2 on the edges. So we may handle a modicum of doglegs. * Bug; In GCell::addBlockage(), removeContact(), removeHSegment() and removeVSegment(), forgot to set the Invalidated flag. This may have lead to innacurate densities. * Change: In GCell::updateDensity(), more complex setting of the GoStraight flag. This flag is now set if we don't have two *contiguous* below 60% of density. We need free contiguous layers to make doglegs. * New: In NetBuilder, now manage a current state flag along with the state flag of the *source* GCell. This flag is used to tell if the GCell needs it's *global* routing to be done using the upper layers (METAL4 & METAL5) instead of the lower ones. * New: In NetBuilder::setStartHook(), set the state flag of the GCell to ToUpperRouting when processing a global routing articulation and one of the base layer is obstructed above 0.9. In GCell with terminals, also set ToUpperRouting when there are some in METAL2 / METAL3 and the gauge is not super-pitched. * New: In NetBuilder, function isInsideBlockage(), to check if a terminal is completely or partially enclosed in a blockage. * Change: In NetBuilderHV::doRp_AutoContact(), remove support for trying to put on grid misaligned METAL2/METAL3. Instead systematically access them from above. Do not cover with fixed protection terminals that are already enclosed in blockages. * Bug: In NetBuilderHV::doRp_AutoContact(), always add the terminal contact in the requested GCell and not the target/source one, in case the terminal span several GCells. * Change: In NetBuilderHV::doRp_Access(), create the local wiring according to the RoutingPad layer. * Change: In NetBuilderHV::_do_xG(), _do_2G(), create the global wiring in upper layers, according to the ToUpperRouting flag. * Change: In NetBuilderHV::_do_xG_xM3(), now delegate to _do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() if the density at terminal level is above 0.5. * New: NetBuilderHV::_do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() separated function to manage the local routing. * Change: In NetBuilder::_do_globalSegment(), if the currently processed GCell or it's source is in ToUpperRouting mode, move up the global segment. Do *not* use the moveUp() function which would create doglegs unwanted at this stage. * New: In KatanaEngine::annotateGlobalGraph(), call postGlobalAnnotate() on the GCell after the blockages have been taken into accound to add the penalty. * Bug: In Track::getPrevious(), correctly manage the 0 value for the index argument. Strange it didn't show earlier. Same goes for Track::expandFreeInterval().
2022-04-27 14:56:41 -05:00
if ( (rpDepth != 0) or (sourcePosition == targetPosition) ) {
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
map<Component*,AutoSegment*>::iterator irp = getRpLookup().find( rp );
if (irp == getRpLookup().end()) {
AutoContact* sourceProtect = AutoContactTerminal::create( sourceGCell
, rp
, rpLayer
, sourcePosition
, viaSide, viaSide
);
AutoContact* targetProtect = AutoContactTerminal::create( targetGCell
, rp
, rpLayer
, targetPosition
, viaSide, viaSide
);
sourceProtect->setFlags( CntFixed );
targetProtect->setFlags( CntFixed );
AutoSegment* segment = AutoSegment::create( sourceProtect, targetProtect, direction );
segment->setFlags( AutoSegment::SegFixed );
getRpLookup().insert( make_pair(rp,segment) );
}
}
if (sourcePosition != targetPosition) {
if (flags & DoSourceContact)
source = AutoContactTerminal::create( sourceGCell
, rp
, rpLayer
, sourcePosition
, viaSide, viaSide
);
if (flags & DoTargetContact)
target = AutoContactTerminal::create( targetGCell
, rp
, rpLayer
, targetPosition
, viaSide, viaSide
);
}
Added direct management of macro blocks I/O pins in METAL2 & METAL3. The decoupling of the cell gauge and the routing gauge implies that the METAL2 & METAL3 terminals of macro blocks cannot be aligned on the routing tracks anymore. That is, an horizontal METAL2 terminal will not be on a track axis, but offgrid, so we no longer can use a METAL2 horizontal segment to connect to it. Making an adjustement between the offgrid terminal and the on-grid segment has proven too complex and generating difficult configuration for the router. Moreover, METLA2 terminal could be fully inside a METAL2 blockage. So now, when the gauges are decoupled, we connect the METAL2 and METAL3 the same way we do for METAL1: *from above* in the perpandicular direction and using a *sliding* VIA. We assume that those kind of terminals in upper metals are quite long. * New: In Hurricane::Rectilinear, export the isNonRectangle() method to the Python interface. * New: In CRL::RoutingGauge, add function isSuperPitched() with the associated boolean attribute. Set to true when each pitch of each layer is independant (not low fractional multiples). * New: In AnabaticEngine, add the ability to temporarily disable the canonize() operation (mainly used in dogleg creation). * New: In AutoSegment::canonize(), do nothing if the operation is disabled by AnabaticEngine. * Bug: In Session::_revalidateTopology(), disable the canonization during the topology updating of a net. Too early canonization was occuring in makeDogleg() leading to incoherencies when performing the later canonization stage over the complete net. Mostly occured in the initial build stage of the net. * New: In GCell, add function postGlobalAnnotate(), if a layer is fully blocked (above 0.9), typically, under a blockage, add a further capacity decrease of 2 on the edges. So we may handle a modicum of doglegs. * Bug; In GCell::addBlockage(), removeContact(), removeHSegment() and removeVSegment(), forgot to set the Invalidated flag. This may have lead to innacurate densities. * Change: In GCell::updateDensity(), more complex setting of the GoStraight flag. This flag is now set if we don't have two *contiguous* below 60% of density. We need free contiguous layers to make doglegs. * New: In NetBuilder, now manage a current state flag along with the state flag of the *source* GCell. This flag is used to tell if the GCell needs it's *global* routing to be done using the upper layers (METAL4 & METAL5) instead of the lower ones. * New: In NetBuilder::setStartHook(), set the state flag of the GCell to ToUpperRouting when processing a global routing articulation and one of the base layer is obstructed above 0.9. In GCell with terminals, also set ToUpperRouting when there are some in METAL2 / METAL3 and the gauge is not super-pitched. * New: In NetBuilder, function isInsideBlockage(), to check if a terminal is completely or partially enclosed in a blockage. * Change: In NetBuilderHV::doRp_AutoContact(), remove support for trying to put on grid misaligned METAL2/METAL3. Instead systematically access them from above. Do not cover with fixed protection terminals that are already enclosed in blockages. * Bug: In NetBuilderHV::doRp_AutoContact(), always add the terminal contact in the requested GCell and not the target/source one, in case the terminal span several GCells. * Change: In NetBuilderHV::doRp_Access(), create the local wiring according to the RoutingPad layer. * Change: In NetBuilderHV::_do_xG(), _do_2G(), create the global wiring in upper layers, according to the ToUpperRouting flag. * Change: In NetBuilderHV::_do_xG_xM3(), now delegate to _do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() if the density at terminal level is above 0.5. * New: NetBuilderHV::_do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() separated function to manage the local routing. * Change: In NetBuilder::_do_globalSegment(), if the currently processed GCell or it's source is in ToUpperRouting mode, move up the global segment. Do *not* use the moveUp() function which would create doglegs unwanted at this stage. * New: In KatanaEngine::annotateGlobalGraph(), call postGlobalAnnotate() on the GCell after the blockages have been taken into accound to add the penalty. * Bug: In Track::getPrevious(), correctly manage the 0 value for the index argument. Strange it didn't show earlier. Same goes for Track::expandFreeInterval().
2022-04-27 14:56:41 -05:00
if ( (rpDepth > 0) and not Session::getRoutingGauge()->isSuperPitched() ) {
rpLayer = Session::getContactLayer( rpDepth );
}
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
if (not source and not target) {
source = target = AutoContactTerminal::create( gcell
, rp
, rpLayer
, rp->getCenter()
, viaSide, viaSide
);
}
cdebug_tabw(145,-1);
return;
}
AutoContact* NetBuilderVH::doRp_Access ( GCell* gcell, Component* rp, uint64_t flags )
{
cdebug_log(145,1) << getTypeName() << "::doRp_Access() - flags:" << flags << endl;
Added direct management of macro blocks I/O pins in METAL2 & METAL3. The decoupling of the cell gauge and the routing gauge implies that the METAL2 & METAL3 terminals of macro blocks cannot be aligned on the routing tracks anymore. That is, an horizontal METAL2 terminal will not be on a track axis, but offgrid, so we no longer can use a METAL2 horizontal segment to connect to it. Making an adjustement between the offgrid terminal and the on-grid segment has proven too complex and generating difficult configuration for the router. Moreover, METLA2 terminal could be fully inside a METAL2 blockage. So now, when the gauges are decoupled, we connect the METAL2 and METAL3 the same way we do for METAL1: *from above* in the perpandicular direction and using a *sliding* VIA. We assume that those kind of terminals in upper metals are quite long. * New: In Hurricane::Rectilinear, export the isNonRectangle() method to the Python interface. * New: In CRL::RoutingGauge, add function isSuperPitched() with the associated boolean attribute. Set to true when each pitch of each layer is independant (not low fractional multiples). * New: In AnabaticEngine, add the ability to temporarily disable the canonize() operation (mainly used in dogleg creation). * New: In AutoSegment::canonize(), do nothing if the operation is disabled by AnabaticEngine. * Bug: In Session::_revalidateTopology(), disable the canonization during the topology updating of a net. Too early canonization was occuring in makeDogleg() leading to incoherencies when performing the later canonization stage over the complete net. Mostly occured in the initial build stage of the net. * New: In GCell, add function postGlobalAnnotate(), if a layer is fully blocked (above 0.9), typically, under a blockage, add a further capacity decrease of 2 on the edges. So we may handle a modicum of doglegs. * Bug; In GCell::addBlockage(), removeContact(), removeHSegment() and removeVSegment(), forgot to set the Invalidated flag. This may have lead to innacurate densities. * Change: In GCell::updateDensity(), more complex setting of the GoStraight flag. This flag is now set if we don't have two *contiguous* below 60% of density. We need free contiguous layers to make doglegs. * New: In NetBuilder, now manage a current state flag along with the state flag of the *source* GCell. This flag is used to tell if the GCell needs it's *global* routing to be done using the upper layers (METAL4 & METAL5) instead of the lower ones. * New: In NetBuilder::setStartHook(), set the state flag of the GCell to ToUpperRouting when processing a global routing articulation and one of the base layer is obstructed above 0.9. In GCell with terminals, also set ToUpperRouting when there are some in METAL2 / METAL3 and the gauge is not super-pitched. * New: In NetBuilder, function isInsideBlockage(), to check if a terminal is completely or partially enclosed in a blockage. * Change: In NetBuilderHV::doRp_AutoContact(), remove support for trying to put on grid misaligned METAL2/METAL3. Instead systematically access them from above. Do not cover with fixed protection terminals that are already enclosed in blockages. * Bug: In NetBuilderHV::doRp_AutoContact(), always add the terminal contact in the requested GCell and not the target/source one, in case the terminal span several GCells. * Change: In NetBuilderHV::doRp_Access(), create the local wiring according to the RoutingPad layer. * Change: In NetBuilderHV::_do_xG(), _do_2G(), create the global wiring in upper layers, according to the ToUpperRouting flag. * Change: In NetBuilderHV::_do_xG_xM3(), now delegate to _do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() if the density at terminal level is above 0.5. * New: NetBuilderHV::_do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() separated function to manage the local routing. * Change: In NetBuilder::_do_globalSegment(), if the currently processed GCell or it's source is in ToUpperRouting mode, move up the global segment. Do *not* use the moveUp() function which would create doglegs unwanted at this stage. * New: In KatanaEngine::annotateGlobalGraph(), call postGlobalAnnotate() on the GCell after the blockages have been taken into accound to add the penalty. * Bug: In Track::getPrevious(), correctly manage the 0 value for the index argument. Strange it didn't show earlier. Same goes for Track::expandFreeInterval().
2022-04-27 14:56:41 -05:00
AutoContact* rpContactSource = NULL;
AutoContact* rpContactTarget = NULL;
const Layer* rpLayer = rp->getLayer();
size_t rpDepth = Session::getLayerDepth( rp->getLayer() );
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
flags |= checkRoutingPadSize( rp );
doRp_AutoContacts( gcell, rp, rpContactSource, rpContactTarget, flags );
Added direct management of macro blocks I/O pins in METAL2 & METAL3. The decoupling of the cell gauge and the routing gauge implies that the METAL2 & METAL3 terminals of macro blocks cannot be aligned on the routing tracks anymore. That is, an horizontal METAL2 terminal will not be on a track axis, but offgrid, so we no longer can use a METAL2 horizontal segment to connect to it. Making an adjustement between the offgrid terminal and the on-grid segment has proven too complex and generating difficult configuration for the router. Moreover, METLA2 terminal could be fully inside a METAL2 blockage. So now, when the gauges are decoupled, we connect the METAL2 and METAL3 the same way we do for METAL1: *from above* in the perpandicular direction and using a *sliding* VIA. We assume that those kind of terminals in upper metals are quite long. * New: In Hurricane::Rectilinear, export the isNonRectangle() method to the Python interface. * New: In CRL::RoutingGauge, add function isSuperPitched() with the associated boolean attribute. Set to true when each pitch of each layer is independant (not low fractional multiples). * New: In AnabaticEngine, add the ability to temporarily disable the canonize() operation (mainly used in dogleg creation). * New: In AutoSegment::canonize(), do nothing if the operation is disabled by AnabaticEngine. * Bug: In Session::_revalidateTopology(), disable the canonization during the topology updating of a net. Too early canonization was occuring in makeDogleg() leading to incoherencies when performing the later canonization stage over the complete net. Mostly occured in the initial build stage of the net. * New: In GCell, add function postGlobalAnnotate(), if a layer is fully blocked (above 0.9), typically, under a blockage, add a further capacity decrease of 2 on the edges. So we may handle a modicum of doglegs. * Bug; In GCell::addBlockage(), removeContact(), removeHSegment() and removeVSegment(), forgot to set the Invalidated flag. This may have lead to innacurate densities. * Change: In GCell::updateDensity(), more complex setting of the GoStraight flag. This flag is now set if we don't have two *contiguous* below 60% of density. We need free contiguous layers to make doglegs. * New: In NetBuilder, now manage a current state flag along with the state flag of the *source* GCell. This flag is used to tell if the GCell needs it's *global* routing to be done using the upper layers (METAL4 & METAL5) instead of the lower ones. * New: In NetBuilder::setStartHook(), set the state flag of the GCell to ToUpperRouting when processing a global routing articulation and one of the base layer is obstructed above 0.9. In GCell with terminals, also set ToUpperRouting when there are some in METAL2 / METAL3 and the gauge is not super-pitched. * New: In NetBuilder, function isInsideBlockage(), to check if a terminal is completely or partially enclosed in a blockage. * Change: In NetBuilderHV::doRp_AutoContact(), remove support for trying to put on grid misaligned METAL2/METAL3. Instead systematically access them from above. Do not cover with fixed protection terminals that are already enclosed in blockages. * Bug: In NetBuilderHV::doRp_AutoContact(), always add the terminal contact in the requested GCell and not the target/source one, in case the terminal span several GCells. * Change: In NetBuilderHV::doRp_Access(), create the local wiring according to the RoutingPad layer. * Change: In NetBuilderHV::_do_xG(), _do_2G(), create the global wiring in upper layers, according to the ToUpperRouting flag. * Change: In NetBuilderHV::_do_xG_xM3(), now delegate to _do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() if the density at terminal level is above 0.5. * New: NetBuilderHV::_do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() separated function to manage the local routing. * Change: In NetBuilder::_do_globalSegment(), if the currently processed GCell or it's source is in ToUpperRouting mode, move up the global segment. Do *not* use the moveUp() function which would create doglegs unwanted at this stage. * New: In KatanaEngine::annotateGlobalGraph(), call postGlobalAnnotate() on the GCell after the blockages have been taken into accound to add the penalty. * Bug: In Track::getPrevious(), correctly manage the 0 value for the index argument. Strange it didn't show earlier. Same goes for Track::expandFreeInterval().
2022-04-27 14:56:41 -05:00
if (rpDepth % 2 == 0) { // RP should be vertical (M1, M3).
if (not (flags & (HAccess|HAccessEW))) {
AutoContact* subContact1 = AutoContactTurn::create( gcell, rp->getNet(), Session::getContactLayer(rpDepth+1) );
AutoContact* subContact2 = AutoContactTurn::create( gcell, rp->getNet(), Session::getContactLayer(rpDepth+1) );
AutoSegment::create( rpContactSource, subContact1, Flags::Vertical , rpDepth+2 );
AutoSegment::create( subContact1, subContact2, Flags::Horizontal, rpDepth+1 );
rpContactSource = subContact2;
} else {
if (flags & VSmall) {
AutoContact* subContact1 = NULL;
if (flags & HAccessEW)
subContact1 = AutoContactHTee::create( gcell, rp->getNet(), Session::getContactLayer(rpDepth+1) );
else
subContact1 = AutoContactTurn::create( gcell, rp->getNet(), Session::getContactLayer(rpDepth+1) );
AutoSegment::create( rpContactSource, subContact1, Flags::Vertical );
rpContactSource = subContact1;
}
}
} else { // RP should be horizontal (M2).
if (flags & (HAccess|HAccessEW)) {
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
AutoContact* subContact1 = NULL;
if (flags & HAccessEW)
Added direct management of macro blocks I/O pins in METAL2 & METAL3. The decoupling of the cell gauge and the routing gauge implies that the METAL2 & METAL3 terminals of macro blocks cannot be aligned on the routing tracks anymore. That is, an horizontal METAL2 terminal will not be on a track axis, but offgrid, so we no longer can use a METAL2 horizontal segment to connect to it. Making an adjustement between the offgrid terminal and the on-grid segment has proven too complex and generating difficult configuration for the router. Moreover, METLA2 terminal could be fully inside a METAL2 blockage. So now, when the gauges are decoupled, we connect the METAL2 and METAL3 the same way we do for METAL1: *from above* in the perpandicular direction and using a *sliding* VIA. We assume that those kind of terminals in upper metals are quite long. * New: In Hurricane::Rectilinear, export the isNonRectangle() method to the Python interface. * New: In CRL::RoutingGauge, add function isSuperPitched() with the associated boolean attribute. Set to true when each pitch of each layer is independant (not low fractional multiples). * New: In AnabaticEngine, add the ability to temporarily disable the canonize() operation (mainly used in dogleg creation). * New: In AutoSegment::canonize(), do nothing if the operation is disabled by AnabaticEngine. * Bug: In Session::_revalidateTopology(), disable the canonization during the topology updating of a net. Too early canonization was occuring in makeDogleg() leading to incoherencies when performing the later canonization stage over the complete net. Mostly occured in the initial build stage of the net. * New: In GCell, add function postGlobalAnnotate(), if a layer is fully blocked (above 0.9), typically, under a blockage, add a further capacity decrease of 2 on the edges. So we may handle a modicum of doglegs. * Bug; In GCell::addBlockage(), removeContact(), removeHSegment() and removeVSegment(), forgot to set the Invalidated flag. This may have lead to innacurate densities. * Change: In GCell::updateDensity(), more complex setting of the GoStraight flag. This flag is now set if we don't have two *contiguous* below 60% of density. We need free contiguous layers to make doglegs. * New: In NetBuilder, now manage a current state flag along with the state flag of the *source* GCell. This flag is used to tell if the GCell needs it's *global* routing to be done using the upper layers (METAL4 & METAL5) instead of the lower ones. * New: In NetBuilder::setStartHook(), set the state flag of the GCell to ToUpperRouting when processing a global routing articulation and one of the base layer is obstructed above 0.9. In GCell with terminals, also set ToUpperRouting when there are some in METAL2 / METAL3 and the gauge is not super-pitched. * New: In NetBuilder, function isInsideBlockage(), to check if a terminal is completely or partially enclosed in a blockage. * Change: In NetBuilderHV::doRp_AutoContact(), remove support for trying to put on grid misaligned METAL2/METAL3. Instead systematically access them from above. Do not cover with fixed protection terminals that are already enclosed in blockages. * Bug: In NetBuilderHV::doRp_AutoContact(), always add the terminal contact in the requested GCell and not the target/source one, in case the terminal span several GCells. * Change: In NetBuilderHV::doRp_Access(), create the local wiring according to the RoutingPad layer. * Change: In NetBuilderHV::_do_xG(), _do_2G(), create the global wiring in upper layers, according to the ToUpperRouting flag. * Change: In NetBuilderHV::_do_xG_xM3(), now delegate to _do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() if the density at terminal level is above 0.5. * New: NetBuilderHV::_do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() separated function to manage the local routing. * Change: In NetBuilder::_do_globalSegment(), if the currently processed GCell or it's source is in ToUpperRouting mode, move up the global segment. Do *not* use the moveUp() function which would create doglegs unwanted at this stage. * New: In KatanaEngine::annotateGlobalGraph(), call postGlobalAnnotate() on the GCell after the blockages have been taken into accound to add the penalty. * Bug: In Track::getPrevious(), correctly manage the 0 value for the index argument. Strange it didn't show earlier. Same goes for Track::expandFreeInterval().
2022-04-27 14:56:41 -05:00
subContact1 = AutoContactHTee::create( gcell, rp->getNet(), Session::getContactLayer(rpDepth+1) );
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
else
Added direct management of macro blocks I/O pins in METAL2 & METAL3. The decoupling of the cell gauge and the routing gauge implies that the METAL2 & METAL3 terminals of macro blocks cannot be aligned on the routing tracks anymore. That is, an horizontal METAL2 terminal will not be on a track axis, but offgrid, so we no longer can use a METAL2 horizontal segment to connect to it. Making an adjustement between the offgrid terminal and the on-grid segment has proven too complex and generating difficult configuration for the router. Moreover, METLA2 terminal could be fully inside a METAL2 blockage. So now, when the gauges are decoupled, we connect the METAL2 and METAL3 the same way we do for METAL1: *from above* in the perpandicular direction and using a *sliding* VIA. We assume that those kind of terminals in upper metals are quite long. * New: In Hurricane::Rectilinear, export the isNonRectangle() method to the Python interface. * New: In CRL::RoutingGauge, add function isSuperPitched() with the associated boolean attribute. Set to true when each pitch of each layer is independant (not low fractional multiples). * New: In AnabaticEngine, add the ability to temporarily disable the canonize() operation (mainly used in dogleg creation). * New: In AutoSegment::canonize(), do nothing if the operation is disabled by AnabaticEngine. * Bug: In Session::_revalidateTopology(), disable the canonization during the topology updating of a net. Too early canonization was occuring in makeDogleg() leading to incoherencies when performing the later canonization stage over the complete net. Mostly occured in the initial build stage of the net. * New: In GCell, add function postGlobalAnnotate(), if a layer is fully blocked (above 0.9), typically, under a blockage, add a further capacity decrease of 2 on the edges. So we may handle a modicum of doglegs. * Bug; In GCell::addBlockage(), removeContact(), removeHSegment() and removeVSegment(), forgot to set the Invalidated flag. This may have lead to innacurate densities. * Change: In GCell::updateDensity(), more complex setting of the GoStraight flag. This flag is now set if we don't have two *contiguous* below 60% of density. We need free contiguous layers to make doglegs. * New: In NetBuilder, now manage a current state flag along with the state flag of the *source* GCell. This flag is used to tell if the GCell needs it's *global* routing to be done using the upper layers (METAL4 & METAL5) instead of the lower ones. * New: In NetBuilder::setStartHook(), set the state flag of the GCell to ToUpperRouting when processing a global routing articulation and one of the base layer is obstructed above 0.9. In GCell with terminals, also set ToUpperRouting when there are some in METAL2 / METAL3 and the gauge is not super-pitched. * New: In NetBuilder, function isInsideBlockage(), to check if a terminal is completely or partially enclosed in a blockage. * Change: In NetBuilderHV::doRp_AutoContact(), remove support for trying to put on grid misaligned METAL2/METAL3. Instead systematically access them from above. Do not cover with fixed protection terminals that are already enclosed in blockages. * Bug: In NetBuilderHV::doRp_AutoContact(), always add the terminal contact in the requested GCell and not the target/source one, in case the terminal span several GCells. * Change: In NetBuilderHV::doRp_Access(), create the local wiring according to the RoutingPad layer. * Change: In NetBuilderHV::_do_xG(), _do_2G(), create the global wiring in upper layers, according to the ToUpperRouting flag. * Change: In NetBuilderHV::_do_xG_xM3(), now delegate to _do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() if the density at terminal level is above 0.5. * New: NetBuilderHV::_do_xG_xM3_baseRouting() and _do_xG_xM3_upperRouting() separated function to manage the local routing. * Change: In NetBuilder::_do_globalSegment(), if the currently processed GCell or it's source is in ToUpperRouting mode, move up the global segment. Do *not* use the moveUp() function which would create doglegs unwanted at this stage. * New: In KatanaEngine::annotateGlobalGraph(), call postGlobalAnnotate() on the GCell after the blockages have been taken into accound to add the penalty. * Bug: In Track::getPrevious(), correctly manage the 0 value for the index argument. Strange it didn't show earlier. Same goes for Track::expandFreeInterval().
2022-04-27 14:56:41 -05:00
subContact1 = AutoContactTurn::create( gcell, rp->getNet(), Session::getContactLayer(rpDepth+1) );
AutoSegment::create( rpContactSource, subContact1, Flags::Vertical, rpDepth+1 );
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
rpContactSource = subContact1;
}
}
cdebug_tabw(145,-1);
return rpContactSource;
}
Pin management implemented for NetBuilderHV. * Bug: In Katana::Track::expandFreeInterval(), the OutsideElement case was not handled correctly, the end index must be increased in that case. As a result, this function was returning too short an interval. This was affecting the computation of perpandicular free interval in DataNegociate::update() for perpandicular fixed but not in a track. * New: In Anabatic::NetBuilder and NetBuilderVH, now manage GCells with one Pin, and up to three globals. Used to put terminals at the edge of a block. * New: In EtesianEngine, now manage placed Pins. (done through extractInstanceName()) * Change: In CRL::RoutingGauge::getHorizontalGauge() no longer skip PinOnly gauges to find the reference one (same goes for vertical).
2019-03-10 07:25:43 -05:00
bool NetBuilderVH::_do_1G_1PinM2 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_1G_1PinM2() [Managed Configuration - Optimized] " << getTopology() << endl;
Pin* pin = dynamic_cast<Pin*>( getRoutingPads()[0]->getOccurrence().getEntity() );
if ( (pin->getAccessDirection() != Pin::AccessDirection::SOUTH)
and (pin->getAccessDirection() != Pin::AccessDirection::NORTH) ) {
cerr << Error( "%s::do_1G_1PinM2(): %s *must* be north or south."
, getTypeName().c_str()
, getString(pin).c_str() ) << endl;
}
uint64_t flags = NoFlags;
if (east()) { flags |= HAccess|VSmall; }
else if (west()) { flags |= HAccess|VSmall; }
setBothCornerContacts( doRp_Access(getGCell(),getRoutingPads()[0],flags) );
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderVH::_do_xG_1PinM2 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_xG_1PinM2() [Managed Configuration] " << getTopology() << endl;
Pin* pin = dynamic_cast<Pin*>( getRoutingPads()[0]->getOccurrence().getEntity() );
if ( (pin->getAccessDirection() != Pin::AccessDirection::SOUTH)
and (pin->getAccessDirection() != Pin::AccessDirection::NORTH) ) {
cerr << Error( "%s::do_xG_1PinM2(): %s *must* be north or south."
, getTypeName().c_str()
, getString(pin).c_str() ) << endl;
}
RoutingPad* rp = getRoutingPads()[0];
AutoContact* pinContact = NULL;
doRp_AutoContacts( getGCell(), rp, pinContact, pinContact, HSmall|VSmall );
if (not north() and not south()) {
AutoContact* subContact1 = AutoContactHTee::create( getGCell(), rp->getNet(), Session::getContactLayer(1) );
AutoSegment::create( pinContact, subContact1, Flags::Vertical );
setBothCornerContacts( subContact1 );
} else {
AutoContact* subContact1 = AutoContactVTee::create( getGCell(), rp->getNet(), Session::getContactLayer(1) );
AutoSegment::create( pinContact, subContact1, Flags::Vertical );
if (east() and west()) {
AutoContact* subContact2 = AutoContactVTee::create( getGCell(), rp->getNet(), Session::getContactLayer(1) );
AutoSegment::create( subContact1, subContact2, Flags::Vertical );
setSouthWestContact( (south()) ? subContact1 : subContact2 );
setNorthEastContact( (south()) ? subContact2 : subContact1 );
} else
setBothCornerContacts( subContact1 );
}
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderVH::_do_1G_1PinM3 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_1G_1PinM3() [Managed Configuration - Optimized] " << getTopology() << endl;
Pin* pin = dynamic_cast<Pin*>( getRoutingPads()[0]->getOccurrence().getEntity() );
if ( (pin->getAccessDirection() != Pin::AccessDirection::EAST)
and (pin->getAccessDirection() != Pin::AccessDirection::WEST) ) {
cerr << Error( "%s::do_1G_1PinM2(): %s *must* be east or west."
, getTypeName().c_str()
, getString(pin).c_str() ) << endl;
}
AutoContact* pinContact = NULL;
doRp_AutoContacts( getGCell(), getRoutingPads()[0], pinContact, pinContact, HSmall|VSmall );
if (east() or west()) {
AutoContact* subContact1 = AutoContactTurn::create( getGCell(), getRoutingPads()[0]->getNet(), Session::getContactLayer(1) );
AutoContact* subContact2 = AutoContactTurn::create( getGCell(), getRoutingPads()[0]->getNet(), Session::getContactLayer(1) );
AutoSegment::create( pinContact , subContact1, Flags::Horizontal );
AutoSegment::create( subContact1, subContact2, Flags::Vertical );
pinContact = subContact2;
} else {
AutoContact* subContact1 = NULL;
subContact1 = AutoContactTurn::create( getGCell(), getRoutingPads()[0]->getNet(), Session::getContactLayer(1) );
AutoSegment::create( pinContact, subContact1, Flags::Horizontal );
pinContact = subContact1;
}
setBothCornerContacts( pinContact );
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderVH::_do_xG_1PinM3 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_xG_1PinM3() [Managed Configuration] " << getTopology() << endl;
RoutingPad* rp = getRoutingPads()[0];
Pin* pin = dynamic_cast<Pin*>( rp->getOccurrence().getEntity() );
if ( (pin->getAccessDirection() != Pin::AccessDirection::EAST)
and (pin->getAccessDirection() != Pin::AccessDirection::WEST) ) {
cerr << Error( "%s::do_xG_1PinM3(): %s *must* be east or west."
, getTypeName().c_str()
, getString(pin).c_str() ) << endl;
}
AutoContact* pinContact = NULL;
doRp_AutoContacts( getGCell(), rp, pinContact, pinContact, HSmall|VSmall );
if (not east() and not west()) {
AutoContact* subContact1 = AutoContactVTee::create( getGCell(), rp->getNet(), Session::getContactLayer(1) );
AutoSegment::create( pinContact, subContact1, Flags::Horizontal );
setBothCornerContacts( subContact1 );
} else {
AutoContact* subContact1 = AutoContactHTee::create( getGCell(), rp->getNet(), Session::getContactLayer(1) );
AutoSegment::create( pinContact, subContact1, Flags::Horizontal );
if (north() and south()) {
AutoContact* subContact2 = AutoContactHTee::create( getGCell(), rp->getNet(), Session::getContactLayer(1) );
AutoSegment::create( subContact1, subContact2, Flags::Horizontal );
setSouthWestContact( (west()) ? subContact1 : subContact2 );
setNorthEastContact( (west()) ? subContact2 : subContact1 );
} else
setBothCornerContacts( subContact1 );
}
cdebug_tabw(145,-1);
return true;
}
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
bool NetBuilderVH::_do_1G_1M1 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_1G_1M1() [Managed Configuration - Optimized] " << getTopology() << endl;
uint64_t flags = NoFlags;
Pin management implemented for NetBuilderHV. * Bug: In Katana::Track::expandFreeInterval(), the OutsideElement case was not handled correctly, the end index must be increased in that case. As a result, this function was returning too short an interval. This was affecting the computation of perpandicular free interval in DataNegociate::update() for perpandicular fixed but not in a track. * New: In Anabatic::NetBuilder and NetBuilderVH, now manage GCells with one Pin, and up to three globals. Used to put terminals at the edge of a block. * New: In EtesianEngine, now manage placed Pins. (done through extractInstanceName()) * Change: In CRL::RoutingGauge::getHorizontalGauge() no longer skip PinOnly gauges to find the reference one (same goes for vertical).
2019-03-10 07:25:43 -05:00
if (east()) { flags |= HAccess|VSmall; }
else if (west()) { flags |= HAccess|VSmall; }
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
setBothCornerContacts( doRp_Access(getGCell(),getRoutingPads()[0],flags) );
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderVH::_do_1G_xM1 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_1G_" << (int)getConnexity().fields.M1 << "M1() [Defered Configuration]" << endl;
_do_xG_xM1_xM3();
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderVH::_do_2G_1M1 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_2G_1M1 [Managed Configuration]" << endl;
cdebug_log(145,0) << "north: " << north() << endl;
cdebug_log(145,0) << "south: " << south() << endl;
cdebug_log(145,0) << "east: " << east() << endl;
cdebug_log(145,0) << "west: " << west() << endl;
AutoContact* tee = NULL;
if (east() and west()) {
tee = doRp_Access( getGCell(), getRoutingPads()[0], HAccessEW|VSmall );
} else {
AutoContact* turn = doRp_Access( getGCell(), getRoutingPads()[0], HAccess|VSmall );
if (east() or west())
tee = AutoContactHTee::create( getGCell(), getNet(), Session::getDContactLayer() );
else
tee = AutoContactVTee::create( getGCell(), getNet(), Session::getDContactLayer() );
AutoSegment::create( turn, tee, Flags::Horizontal );
}
setBothCornerContacts( tee );
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderVH::_do_xG_xM1_xM3 ()
{
Basic support for FreePDK 45 completed. * New: In Commons, inspector support for std::pair<T,U>. * New: In Hurricane::Layer, ContactLayer & ViaLayer, support for non square VIAs. The hole (cut) remains square, but the various metal extensions can now be different in X and Y. The ::getEnclosure() method now takes a flag EnclosureH / EnclosureV. * New: In Hurricane::DbU, inspector support for: std::pair<DbU::Unit,DbU::Unit> std::array<DbU::Unit,3> Must be defined here as DbU do not exists yet in Commons.h * Bug: In Hurricane::Interval::getSize(), when the interval is "full span", do not return the difference between min and max, but directly DbU::Max. (the previous result was -1 !) * New: In CRL Core Python/Technology.py, support for non square VIAs in the configuration files. Applied to FreePDK 45. * New: In CRL::RoutingGauge, added a "symbolic" flag to tell if a gauge is for symbolic layout or not. Exported to Python. * New: In Anabatic::AutoHorizontal::updatePosition(), differentiated computation for soure or target taking account of the VIA extension in the right segment metal (due to non-square VIAs). * Change: In Anabatic::AutoHorizontal::_makeDogleg(), the dogleg is UP for HV gauges and DOWN for VH. * New: In Anabatic::AutoSegment::_initialize(), create a cache of the various extension length for each layer (viaToTop, viaToBottom, viaToSame). New implementation of getExtensionCap() using the previous cached extension table. See updatePositions(). New static functions to access the extension cache in the header: getViaTotopCap() ... * Change: In Anabatic::AutoSegment, in various update methods, updateOrient() must always be called *before* updatePositions() as extensions are dependant on source/target. * New: In Anabatic::AutoSegment::getEndAxes() compute the position of the first source and last target position (center/axes) on an *aligned* set of segments. * New: In Anabatic::AutoSegment, add a new state flag SegAxisFixed to signal segments that can be put on only one track. Specific case to VH gauge for a M1 vertical terminal with a M2 vertical segment. The M2 is effectively bound to the M1 axis position. * Bug: In Anabatic::NetBuilderVH::_do_xG_xM1_xM3(), in case of E/W global and only one RoutingPad the connexion to the RoutingPad was duplicated. It was valid, but totally stupid. * Bug: In Anabatic::Session::_canonize(), for an aligned segment set, intersect the user constraints from all segments instead of only considering the canonical one. Issue a warning about too tight constraints only for symbolic gauges. It may be correct for the real ones. * New: In Katata::DataNegociate::update(), more accurate computation of the perpandicular free interval. Use segment extension cap calculation. Create a special case for fixed axis segments allowing them to find alternative free interval, try under source and under target as they are likely to be draggable segments. * Change: In Katana::Manipulator::relax(), use the extension cap value to compute the axis of the perpandicular segemnts. * Change: In Katana::Manipulator::moveUp(), now move up the whole set of aligned segments instead of just the canonical one. * Change: In Katana::NegociateWindow::loadRoutingPads(), more accurate TrackMarkers insertions for fixed terminals. * New: In Katana::RoutingEvent::Key::Compare::operator(), segments with fixed axis are processed prior to any others. * New: In Katana::RoutingEventLoop, store segment pointers instead of ids to generate more accurate error messages. * Change: In Katana::RoutingPlane::create(), perform local track assignment only for HV gauges. * Change: In Katana::SegmentFsm::_slackenLocal(), add a "dragMinimize" step in the automaton. Mutliple states transitions can occurs in a row if an action fails. * New: In Katana::Session::_toIntervalAxis(), normalize interval bounds so they are on track positions (by shrinking the interval). * Bug: In Katana::TrackMarker CTOR, the weigh computation was wrong.
2018-02-17 13:27:38 -06:00
// Implicit hypothesis : we have at least two globals and at least one terminal.
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
cdebug_log(145,1) << getTypeName()
<< "::_do_xG_" << (int)getConnexity().fields.M1
<< "M1_" << (int)getConnexity().fields.M3
<< "M3() [G:" << (int)getConnexity().fields.globals << " Managed Configuration]" << endl;
cdebug_log(145,0) << "getConnexity(): " << getConnexity().connexity << endl;
cdebug_log(145,0) << "north: " << north() << endl;
cdebug_log(145,0) << "south: " << south() << endl;
cdebug_log(145,0) << "east: " << east() << endl;
cdebug_log(145,0) << "west: " << west() << endl;
sortRpByX( getRoutingPads(), NoFlags ); // increasing X.
size_t iLast = getRoutingPads().size()-1;
AutoContact* leftContact = NULL;
AutoContact* rightContact = NULL;
if (south() or west()) {
leftContact = doRp_Access( getGCell(), getRoutingPads()[0], HAccessEW|VSmall );
if (south() and west()) {
setSouthWestContact( AutoContactHTee::create( getGCell(), getNet(), Session::getDContactLayer() ) );
AutoSegment::create( getSouthWestContact(), leftContact, Flags::Horizontal );
} else {
if (west())
setSouthWestContact( leftContact );
else {
setSouthWestContact( AutoContactTurn::create( getGCell(), getNet(), Session::getDContactLayer() ) );
AutoSegment::create( leftContact, getSouthWestContact(), Flags::Horizontal );
}
}
} else {
leftContact = doRp_Access( getGCell(), getRoutingPads()[0], HAccess|VSmall );
}
for ( size_t i=1 ; i<getRoutingPads().size()-1 ; ++i ) {
rightContact = doRp_Access( getGCell(), getRoutingPads()[i], HAccessEW|VSmall );
AutoSegment::create( leftContact, rightContact, Flags::Horizontal );
leftContact = rightContact;
}
if (north() or east()) {
Basic support for FreePDK 45 completed. * New: In Commons, inspector support for std::pair<T,U>. * New: In Hurricane::Layer, ContactLayer & ViaLayer, support for non square VIAs. The hole (cut) remains square, but the various metal extensions can now be different in X and Y. The ::getEnclosure() method now takes a flag EnclosureH / EnclosureV. * New: In Hurricane::DbU, inspector support for: std::pair<DbU::Unit,DbU::Unit> std::array<DbU::Unit,3> Must be defined here as DbU do not exists yet in Commons.h * Bug: In Hurricane::Interval::getSize(), when the interval is "full span", do not return the difference between min and max, but directly DbU::Max. (the previous result was -1 !) * New: In CRL Core Python/Technology.py, support for non square VIAs in the configuration files. Applied to FreePDK 45. * New: In CRL::RoutingGauge, added a "symbolic" flag to tell if a gauge is for symbolic layout or not. Exported to Python. * New: In Anabatic::AutoHorizontal::updatePosition(), differentiated computation for soure or target taking account of the VIA extension in the right segment metal (due to non-square VIAs). * Change: In Anabatic::AutoHorizontal::_makeDogleg(), the dogleg is UP for HV gauges and DOWN for VH. * New: In Anabatic::AutoSegment::_initialize(), create a cache of the various extension length for each layer (viaToTop, viaToBottom, viaToSame). New implementation of getExtensionCap() using the previous cached extension table. See updatePositions(). New static functions to access the extension cache in the header: getViaTotopCap() ... * Change: In Anabatic::AutoSegment, in various update methods, updateOrient() must always be called *before* updatePositions() as extensions are dependant on source/target. * New: In Anabatic::AutoSegment::getEndAxes() compute the position of the first source and last target position (center/axes) on an *aligned* set of segments. * New: In Anabatic::AutoSegment, add a new state flag SegAxisFixed to signal segments that can be put on only one track. Specific case to VH gauge for a M1 vertical terminal with a M2 vertical segment. The M2 is effectively bound to the M1 axis position. * Bug: In Anabatic::NetBuilderVH::_do_xG_xM1_xM3(), in case of E/W global and only one RoutingPad the connexion to the RoutingPad was duplicated. It was valid, but totally stupid. * Bug: In Anabatic::Session::_canonize(), for an aligned segment set, intersect the user constraints from all segments instead of only considering the canonical one. Issue a warning about too tight constraints only for symbolic gauges. It may be correct for the real ones. * New: In Katata::DataNegociate::update(), more accurate computation of the perpandicular free interval. Use segment extension cap calculation. Create a special case for fixed axis segments allowing them to find alternative free interval, try under source and under target as they are likely to be draggable segments. * Change: In Katana::Manipulator::relax(), use the extension cap value to compute the axis of the perpandicular segemnts. * Change: In Katana::Manipulator::moveUp(), now move up the whole set of aligned segments instead of just the canonical one. * Change: In Katana::NegociateWindow::loadRoutingPads(), more accurate TrackMarkers insertions for fixed terminals. * New: In Katana::RoutingEvent::Key::Compare::operator(), segments with fixed axis are processed prior to any others. * New: In Katana::RoutingEventLoop, store segment pointers instead of ids to generate more accurate error messages. * Change: In Katana::RoutingPlane::create(), perform local track assignment only for HV gauges. * Change: In Katana::SegmentFsm::_slackenLocal(), add a "dragMinimize" step in the automaton. Mutliple states transitions can occurs in a row if an action fails. * New: In Katana::Session::_toIntervalAxis(), normalize interval bounds so they are on track positions (by shrinking the interval). * Bug: In Katana::TrackMarker CTOR, the weigh computation was wrong.
2018-02-17 13:27:38 -06:00
if (getRoutingPads().size() > 1) {
rightContact = doRp_Access( getGCell(), getRoutingPads()[iLast], HAccessEW|VSmall );
AutoSegment::create( leftContact, rightContact, Flags::Horizontal );
} else {
rightContact = leftContact;
}
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
if (north() and east()) {
setNorthEastContact( AutoContactHTee::create( getGCell(), getNet(), Session::getDContactLayer() ) );
AutoSegment::create( rightContact, getNorthEastContact(), Flags::Horizontal );
} else {
if (east())
setNorthEastContact( rightContact );
else {
setNorthEastContact( AutoContactTurn::create( getGCell(), getNet(), Session::getDContactLayer() ) );
AutoSegment::create( rightContact, getNorthEastContact(), Flags::Horizontal );
}
}
} else {
rightContact = doRp_Access( getGCell(), getRoutingPads()[iLast], HAccess|VSmall );
AutoSegment::create( leftContact, rightContact, Flags::Horizontal );
}
cdebug_tabw(145,-1);
return true;
}
Bug fix, restore the FreePDK 45 (real) support. * Change: In CRL::LefParser::_macroCbk(), create a Catalog entry for the newly read MACRO (that is Cell) and sets the Logical, Physical, InMemory and TerminalNetlist flags. * Bug: In CRL::LefParser::_siteCbk(), check for NULL cell gauge. * New: In CRL::AllianceFramework, add setCellGauge(), to set the default cell gauge. Exported to Python. * Change: In CRL/etc/common/technology.py, create variables for VIA layers, so we can modify their properties afterwards. * New: In CRL/etc/node45/freepdk45, port the configuration files to the new Python "importable" format. Note: in kite.py, all the gauges (Routing & Cells) must be named "LEF.CoreSite" to please my LEF parser, so it can match the gauge name with the SITE name for standard cells. * Bug: In Anabatic::NetBuilderVH::_do_2G(), forgotten to be reimplemented from the base class. Simply redirect to _do_xG(). * Change: In Katana::PowerRailsPlanes::PowerRailsplanes(), create plane from the layers in the RoutingGauge and their associated blockages instead of sweeping through all the basic layers. Allow to distinguish bewteen "METAL" (symbolic) and "metal" (real).
2020-04-27 03:34:19 -05:00
bool NetBuilderVH::_do_2G ()
{
cdebug_log(145,0) << getTypeName() << "::_do_2G()" << endl;
return _do_xG();
}
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
bool NetBuilderVH::_do_xG ()
{
cdebug_log(145,1) << getTypeName() << "::_do_xG()" << endl;
const Layer* viaLayer = Session::getDContactLayer();
if (getConnexity().fields.globals == 2) {
setBothCornerContacts( AutoContactTurn::create( getGCell(), getNet(), viaLayer ) );
} else if (getConnexity().fields.globals == 3) {
if (east() and west()) {
setSouthWestContact( AutoContactTurn::create( getGCell(), getNet(), viaLayer ) );
setNorthEastContact( AutoContactVTee::create( getGCell(), getNet(), viaLayer ) );
if (south()) swapCornerContacts();
AutoSegment::create( getSouthWestContact(), getNorthEastContact(), Flags::Vertical );
} else {
setSouthWestContact( AutoContactTurn::create( getGCell(), getNet(), viaLayer ) );
setNorthEastContact( AutoContactHTee::create( getGCell(), getNet(), viaLayer ) );
if (west()) swapCornerContacts();
AutoSegment::create( getSouthWestContact(), getNorthEastContact(), Flags::Horizontal );
}
} else { // fields.globals == 4.
AutoContact* turn = AutoContactTurn::create( getGCell(), getNet(), viaLayer );
setSouthWestContact( AutoContactHTee::create( getGCell(), getNet(), viaLayer ) );
setNorthEastContact( AutoContactVTee::create( getGCell(), getNet(), viaLayer ) );
AutoSegment::create( getSouthWestContact(), turn, Flags::Horizontal );
AutoSegment::create( turn, getNorthEastContact(), Flags::Vertical );
}
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderVH::_do_globalSegment ()
{
cdebug_log(145,1) << getTypeName() << "::_do_globalSegment()" << endl;
if (getSourceContact()) {
AutoContact* targetContact
= ( getSegmentHookType(getFromHook()) & (NorthBound|EastBound) )
? getNorthEastContact() : getSouthWestContact() ;
AutoSegment* globalSegment = AutoSegment::create( getSourceContact()
, targetContact
, static_cast<Segment*>( getFromHook()->getComponent() )
);
globalSegment->setFlags( (getDegree() == 2) ? AutoSegment::SegBipoint : 0 );
cdebug_log(145,0) << "Create global segment: " << globalSegment << endl;
// HARDCODED VALUE.
Rewrite support for minimum area metal wires (stacked VIAs). We use the segments extensions (dxTarget & dyTarget) to enlarge if needed the segments. This new implementation is completely at Anabatic level and should not be seen (i.e. managed) at Katana level. * Change: In AutoHorizontal & AutoVertical, change the semantic of getSourceU() and getTargetU(). formerly they where the end position of the segment (with extension included), now they gives the position of the anchor contacts, that is the axis of the perpandiculars. * New: AutoSegment::getLength() is still a proxy toward the Segment::getLength() which returns the length of segment with dxSource & dxTarget. We introduce a getAnchoredlength() which returns the length between the centers of the S/T anchors. That is axis to axis. This is this length which is now used througout Anabatic. * New: In AutoSegment::_extentionCaps, add a fourth item to hold the segment minimal length (to respect minimal area given the wire width). * New: In AutoSegment::getExtensionCap(), if the segment has a non-zero S/T extension, returns it instead of the S/T contact extension *if it is greated*. The check of the extension can be disabled by the Flag::NoSegExt flag. * Change: In AutoSegment::isMiddleStack(), security check on the presence of source and targets. More accurate detection of perpandicular in "same layer" with a non-zero length, So the area is OK, even with a short segment. * New: AutoSegment::expandToMinLength(), check if a segment is under the minimal length and expand it if need be by playing with the dxTarget & dxSource. Tag minimal segments with the AutoSegment::SegAtMinArea flag. Also try to keep the segment *inside* it's former (supposedly wider) interval. * New: AutoSegment::unexpandToMinLength(), to be called on a formerly minimal sized segment which as grown up. Reset it's S/T extensions to zero and unset the flag SegAtMinArea. * Change: In AutoHorizontal::updateOrient(), when the extension are non-zero, also swap them if needed, to keep the exact footprint of the segment. * New: In AutoSegment::revalidate(), check that the segment respect the minimal length (area), and expand it if needed. Conversely, if the segment has grown up from a minimal length state, reset it's extensions to zero. * Change: In Anabatic::Session::revalidate(), invalidateds segments are now sorted in such a way that the "middle stack" ones are revalidateds last. Not recall 100% why... * New: In Katana::TrackCost, add a computation of the free interval length we are into (if any). Not used yet, keep it for future use. * Change: In KatanaEngine::finalizeLayout(), remove the call to segments minimum area protection. It is now obsoleted by the new implementation in Anabatic. * Change: In Track::check(), call the minimum size/area checker Track::checkMinArea().
2021-04-04 17:01:54 -05:00
if ( (getTopology() & Global_Fixed) and (globalSegment->getAnchoredLength() < 2*Session::getSliceHeight()) )
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
addToFixSegments( globalSegment );
if (getConnexity().fields.globals < 2) {
cdebug_tabw(145,-1);
return false;
}
} else
setFromHook( NULL );
push( east (), getNorthEastContact() );
push( west (), getSouthWestContact() );
push( north(), getNorthEastContact() );
push( south(), getSouthWestContact() );
cdebug_tabw(145,-1);
return true;
}
void NetBuilderVH::singleGCell ( AnabaticEngine* anbt, Net* net )
{
cdebug_log(145,1) << getTypeName() << "::singleGCell() " << net << endl;
vector<RoutingPad*> rps;
for ( RoutingPad* rp : net->getRoutingPads() ) {
if (Session::getRoutingGauge()->getLayerDepth(rp->getLayer()) == 0) {
rps.push_back( rp );
continue;
}
cerr << Error( "%s::singleGCell(): Non metal1 terminals are not managed yet.\n"
" (%s)"
, getTypeName().c_str()
, getString(rp).c_str()
) << endl;
cdebug_tabw(145,-1);
return;
}
if (rps.size() < 2) {
cerr << Error( "%s::singleGCell(): For %s, less than two Plugs/Pins (%d)."
, getTypeName().c_str()
, getString(net).c_str()
, rps.size() ) << endl;
cdebug_tabw(145,-1);
return;
}
if (rps.empty()) {
cerr << Error( "%s::singleGCell(): No terminals for Net \"%s\"."
, getTypeName().c_str()
, getString(net->getName()).c_str() ) << endl;
cdebug_tabw(145,-1);
return;
}
sortRpByX( rps, NetBuilder::NoFlags ); // increasing X.
GCell* gcell1 = anbt->getGCellUnder( (*rps.begin ())->getCenter() );
GCell* gcell2 = anbt->getGCellUnder( (*rps.rbegin())->getCenter() );
if (not gcell1) {
cerr << Error( "%s::singleGCell(): No GCell under %s."
, getTypeName().c_str()
, getString(*(rps.begin())).c_str() ) << endl;
cdebug_tabw(145,-1);
return;
}
if (gcell1 != gcell2) {
cerr << Error( "%s::singleGCell(): Not under a single GCell %s."
, getTypeName().c_str()
, getString(*(rps.rbegin())).c_str() ) << endl;
cdebug_tabw(145,-1);
return;
}
cdebug_log(145,0) << "singleGCell " << gcell1 << endl;
AutoContact* source = NULL;
AutoContact* target = NULL;
for ( size_t irp=1 ; irp<rps.size() ; ++irp ) {
source = doRp_Access( gcell1, rps[irp-1], HAccess|VSmall );
target = doRp_Access( gcell1, rps[irp ], HAccess|VSmall );
AutoSegment::create( source, target, Flags::Horizontal );
}
cdebug_tabw(145,-1);
}
Basic support for FreePDK 45 completed. * New: In Commons, inspector support for std::pair<T,U>. * New: In Hurricane::Layer, ContactLayer & ViaLayer, support for non square VIAs. The hole (cut) remains square, but the various metal extensions can now be different in X and Y. The ::getEnclosure() method now takes a flag EnclosureH / EnclosureV. * New: In Hurricane::DbU, inspector support for: std::pair<DbU::Unit,DbU::Unit> std::array<DbU::Unit,3> Must be defined here as DbU do not exists yet in Commons.h * Bug: In Hurricane::Interval::getSize(), when the interval is "full span", do not return the difference between min and max, but directly DbU::Max. (the previous result was -1 !) * New: In CRL Core Python/Technology.py, support for non square VIAs in the configuration files. Applied to FreePDK 45. * New: In CRL::RoutingGauge, added a "symbolic" flag to tell if a gauge is for symbolic layout or not. Exported to Python. * New: In Anabatic::AutoHorizontal::updatePosition(), differentiated computation for soure or target taking account of the VIA extension in the right segment metal (due to non-square VIAs). * Change: In Anabatic::AutoHorizontal::_makeDogleg(), the dogleg is UP for HV gauges and DOWN for VH. * New: In Anabatic::AutoSegment::_initialize(), create a cache of the various extension length for each layer (viaToTop, viaToBottom, viaToSame). New implementation of getExtensionCap() using the previous cached extension table. See updatePositions(). New static functions to access the extension cache in the header: getViaTotopCap() ... * Change: In Anabatic::AutoSegment, in various update methods, updateOrient() must always be called *before* updatePositions() as extensions are dependant on source/target. * New: In Anabatic::AutoSegment::getEndAxes() compute the position of the first source and last target position (center/axes) on an *aligned* set of segments. * New: In Anabatic::AutoSegment, add a new state flag SegAxisFixed to signal segments that can be put on only one track. Specific case to VH gauge for a M1 vertical terminal with a M2 vertical segment. The M2 is effectively bound to the M1 axis position. * Bug: In Anabatic::NetBuilderVH::_do_xG_xM1_xM3(), in case of E/W global and only one RoutingPad the connexion to the RoutingPad was duplicated. It was valid, but totally stupid. * Bug: In Anabatic::Session::_canonize(), for an aligned segment set, intersect the user constraints from all segments instead of only considering the canonical one. Issue a warning about too tight constraints only for symbolic gauges. It may be correct for the real ones. * New: In Katata::DataNegociate::update(), more accurate computation of the perpandicular free interval. Use segment extension cap calculation. Create a special case for fixed axis segments allowing them to find alternative free interval, try under source and under target as they are likely to be draggable segments. * Change: In Katana::Manipulator::relax(), use the extension cap value to compute the axis of the perpandicular segemnts. * Change: In Katana::Manipulator::moveUp(), now move up the whole set of aligned segments instead of just the canonical one. * Change: In Katana::NegociateWindow::loadRoutingPads(), more accurate TrackMarkers insertions for fixed terminals. * New: In Katana::RoutingEvent::Key::Compare::operator(), segments with fixed axis are processed prior to any others. * New: In Katana::RoutingEventLoop, store segment pointers instead of ids to generate more accurate error messages. * Change: In Katana::RoutingPlane::create(), perform local track assignment only for HV gauges. * Change: In Katana::SegmentFsm::_slackenLocal(), add a "dragMinimize" step in the automaton. Mutliple states transitions can occurs in a row if an action fails. * New: In Katana::Session::_toIntervalAxis(), normalize interval bounds so they are on track positions (by shrinking the interval). * Bug: In Katana::TrackMarker CTOR, the weigh computation was wrong.
2018-02-17 13:27:38 -06:00
In Anabatic/Katana, add support for VH gauges (real technos). * Change: In Anabatic::AutoContactTerminal::getNativeConstraintBox(), when the anchor is a RoutingPad (which must be always the case), perform the true computation of it's position based on the segment occurrence. It is a important change, previously the area was in fact the "center line" of the connector while now it is really an area (mandatory for "half-offgrid" terminals of real technologies). The change is not complete yet, the area should be shrinked by the half size of a VIA, because the area applies to the center coordinate of the VIA (to be done quickly). * Bug: In Anabatic::AutoContactTurn::updateTopology(), when a dogleg is created (restore connexity after a layer change) the layer of the VIA, based on the segments it connects to must be re-computed *after* the dogleg has been made. * Change: In all files of Anabatic, when comparing two layers, no longer use the Layer pointer itself, but the layer mask. This allow a transparent management of both real and symbolic layers (which do share the same mask). Real metal layers (not VIAs) will be BasicLayer and symbolic metal layers will be RegularLayer. * New: Anabatic::Configuration::selectRpComponent(), select the best RoutingPad component for metal1 terminals. Look for the metal1 component with the biggest accessibility on-grid. RoutingPad using other metals are left untoucheds. * New: New function Anabatic::Vertex::getNeighbor(Edge*) to get the neighbor Vertex through an Edge*. This method allows to write clearer code as we no longer need to access the neighbor through the underlying GCell. Also add proxies for GCell methods in Vertex. * Bug: In Anabatic::Dijkstra::_toSources(), in the ripup stage, when a component with multiples vertexes is reached *and* two of it's vertexes are reached *at the same time* (one from which we backtrack and one still in the queue) extraneous edges may be created by _materialize(). Case occurs on snx/c35b4, "abc_5360_n903_1". To solve this, Dijkstra::_toSource() is modificated, the "from" edges of the newly reacheds vertexes are reset to NULL, *except* for the one we will be backtracking from. That is, the one given in the source argument. * Change: In Anabatic::NetBuilder class, put the various Hooks and RoutingPad sorting functions as class ones. * Bug: In AutoSegment::setLayer(), raise the SegInvalidatedFayer flag. This unset flag was causing AutoContactTurn::updateTopology() to not work as expected and making gaps, this was the cause of the last remaining warnings about layer connexity.
2018-01-06 09:55:53 -06:00
string NetBuilderVH::getTypeName () const
{ return "NetBuilderVH"; }
} // Anabatic namespace.