riscv
/
coriolis
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
coriolis/anabatic/src/NetBuilderHybridVH.cpp

644 lines
23 KiB
C++
Raw Normal View History

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
// -*- C++ -*-
//
// This file is part of the Coriolis Software.
// Copyright (c) Sorbonne Université 2022-2022, All Rights Reserved
//
// +-----------------------------------------------------------------+
// | 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 : "./NetBuilderHybridVH.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/Pin.h"
#include "hurricane/Pad.h"
#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/NetBuilderHybridVH.h"
#include "anabatic/AnabaticEngine.h"
namespace Anabatic {
using std::swap;
using Hurricane::Error;
using Hurricane::Pin;
NetBuilderHybridVH::NetBuilderHybridVH ()
: NetBuilder()
{ }
NetBuilderHybridVH::~NetBuilderHybridVH () { }
string NetBuilderHybridVH::getStyle ()
{ return "VH,2RL"; }
void NetBuilderHybridVH::doRp_AutoContacts ( GCell* gcell
, Component* rp
, AutoContact*& source
, AutoContact*& target
, uint64_t flags
)
{
throw Error ( "%s::dpRp_AutoContacts() method must never be called.", getTypeName().c_str() );
}
AutoContact* NetBuilderHybridVH::doRp_Access ( GCell* gcell, Component* rp, uint64_t flags )
{
cdebug_log(145,1) << getTypeName() << "::doRp_Access()" << endl;
cdebug_log(145,0) << rp << endl;
const Layer* rpLayer = rp->getLayer();
Bug in topology management switch in NetBuilder::construct(). * Bug: In NetBuilder::construct(), the xG_xM1 topologies where wrongly redirected towards xG_1M1, so only one M1 was connected, all others left floating. Now direct them towards xG_xM1_xM3. * Bug: In NetBuilderHybridVH, activate topology management for 2G_1M1.
2022-12-16 13:02:11 -06:00
//const Layer* viaLayer = Session::getDContactLayer();
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
DbU::Unit viaSide = Session::getDContactWidth();
Point position = rp->getCenter();
AutoContact* rpContact = AutoContactTerminal::create( gcell, rp, rpLayer, position, viaSide, viaSide );
cdebug_tabw(145,-1);
return rpContact;
}
AutoContact* NetBuilderHybridVH::doRp_AccessNorthSouthPin ( GCell* gcell, RoutingPad* rp )
{
cdebug_log(145,1) << getTypeName() << "::doRp_AccessNorthSouthPin() " << rp << endl;
AutoContact* rpContact = doRp_Access( gcell, rp, NoFlags );
AutoContact* turn = NULL;
Net* net = rp->getNet();
Pin* pin = dynamic_cast<Pin*>( rp->getOccurrence().getEntity() );
Pin::AccessDirection pinDir = pin->getAccessDirection();
if (pinDir == Pin::AccessDirection::NORTH) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
turn = AutoContactTurn::create( gcell, net, Session::getBuildRoutingLayer(0) );
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
AutoSegment* segment = AutoSegment::create( rpContact, turn, Flags::Vertical );
segment->setAxis( rp->getX(), Flags::Force );
segment->setFlags( AutoSegment::SegFixed|AutoSegment::SegFixedAxis );
rpContact = turn;
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
turn = AutoContactTurn::create( gcell, net, Session::getBuildContactLayer(0) );
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
segment = AutoSegment::create( rpContact, turn, Flags::Horizontal );
rpContact = turn;
DbU::Unit axis = gcell->getYMax() - Session::getDHorizontalPitch();
cdebug_log(145,0) << "axis:" << DbU::getValueString(axis) << endl;
segment->setAxis( axis, Flags::Force );
//segment->setFlags( AutoSegment::SegFixed|AutoSegment::SegFixedAxis );
cdebug_log(145,0) << segment << endl;
} else {
turn = rpContact;
}
cdebug_tabw(145,-1);
return turn;
}
AutoContact* NetBuilderHybridVH::doRp_AccessEastWestPin ( GCell* gcell, RoutingPad* rp )
{
cdebug_log(145,1) << getTypeName() << "::doRp_AccessEastWestPin() " << rp << endl;
Net* net = rp->getNet();
Pin* pin = dynamic_cast<Pin*>( rp->getOccurrence().getEntity() );
Pin::AccessDirection pinDir = pin->getAccessDirection();
AutoContact* rpContact = doRp_Access( gcell, rp, NoFlags );
AutoContact* turn = NULL;
AutoSegment* segment = NULL;
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
turn = AutoContactTurn::create( gcell, net, Session::getBuildContactLayer(0) );
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
segment = AutoSegment::create( rpContact, turn, Flags::Horizontal );
segment->setAxis( pin->getCenter().getY(), Flags::Force );
rpContact = turn;
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
turn = AutoContactTurn::create( gcell, net, Session::getBuildContactLayer(0) );
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
segment = AutoSegment::create( rpContact, turn, Flags::Vertical );
DbU::Unit axis = 0;
if (pinDir == Pin::AccessDirection::EAST)
axis = gcell->getXMax() - Session::getDVerticalPitch();
else
axis = gcell->getXMin() + Session::getDVerticalPitch();
segment->setAxis( axis );
cdebug_tabw(145,-1);
return turn;
}
bool NetBuilderHybridVH::doRp_xG_1M1 ( RoutingPad* rp )
{
cdebug_log(145,1) << getTypeName() << "::doRp_xG_1M1()" << endl;
AutoContact* swContact = nullptr;
if (west() or south()) {
AutoContact* termContact = doRp_Access( getGCell(), rp, NoFlags );
if (west() and south()) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
swContact = AutoContactVTee::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( termContact, swContact, Flags::Vertical );
} else {
if (west()) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
swContact = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( termContact, swContact, Flags::Vertical );
} else
swContact = termContact;
}
setSouthWestContact( swContact );
}
AutoContact* neContact = nullptr;
if (east() or north()) {
AutoContact* termContact = doRp_Access( getGCell(), rp, NoFlags );
if (east() and north()) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
neContact = AutoContactVTee::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( termContact, neContact, Flags::Vertical );
} else {
if (east()) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
neContact = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( termContact, neContact, Flags::Vertical );
} else
neContact = termContact;
}
setNorthEastContact( neContact );
}
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderHybridVH::_do_xG_1M1 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_xG_1M1()" << endl;
doRp_xG_1M1( getRoutingPads()[0] );
cdebug_tabw(145,-1);
return true;
}
Bug in topology management switch in NetBuilder::construct(). * Bug: In NetBuilder::construct(), the xG_xM1 topologies where wrongly redirected towards xG_1M1, so only one M1 was connected, all others left floating. Now direct them towards xG_xM1_xM3. * Bug: In NetBuilderHybridVH, activate topology management for 2G_1M1.
2022-12-16 13:02:11 -06:00
bool NetBuilderHybridVH::_do_2G_1M1 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_2G_1M1()" << endl;
doRp_xG_1M1( getRoutingPads()[0] );
cdebug_tabw(145,-1);
return true;
}
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
bool NetBuilderHybridVH::doRp_xG_xM1_xM3 ( const vector<RoutingPad*>& rps )
{
cdebug_log(145,1) << getTypeName() << "::doRp_xG_xM1()" << endl;
AutoContact* prevContact = nullptr;
AutoContact* currContact = nullptr;
for ( size_t i=0 ; i<rps.size() ; ++i ) {
prevContact = currContact;
AutoContact* currTerm = doRp_Access( getGCell(), rps[i], NoFlags );
if (i == 0) {
if (west() or south()) {
AutoContact* swContact = nullptr;
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
currContact = AutoContactVTee::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
if (west() and south()) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
swContact = AutoContactVTee::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
} else {
if (west())
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
swContact = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
else
swContact = currContact;
}
if (swContact != currContact)
AutoSegment::create( currContact, swContact, Flags::Vertical );
setSouthWestContact( swContact );
} else {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
currContact = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
}
AutoSegment::create( currTerm, currContact, Flags::Vertical );
continue;
}
if (i+1 == rps.size()) {
if (east() or north()) {
AutoContact* neContact = nullptr;
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
currContact = AutoContactVTee::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
if (east() and north()) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
neContact = AutoContactVTee::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
} else {
if (east())
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
neContact = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
else
neContact = currContact;
}
if (neContact != currContact)
AutoSegment::create( currContact, neContact, Flags::Vertical );
setNorthEastContact( neContact );
} else {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
currContact = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
}
} else {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
currContact = AutoContactHTee::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
}
Support for avoidance of vertical tracks in low metal techs. * New: In NetBuilderHybridVH::_do_1G_xM1_1PinM1(), added configuration to manage pins on the north/south sides for VH,2RL. * Bug: In NetBuilderHybridVH::doRp_xG_xM1_xM3(), correct misplaced vertical creation (buildind invalid topologies). * New: EtesianEngine::toColoquinte(), display histograms of the cells widths (in pitch) before and after bloating to get a better feeling of the behavior. * New: In EtesianEngine, add support for track avoidance. Portions of tracks to avoid are specified by a Box, which should flat and on the axis of the request track. This feature is used by the H-Tree to clear the vertical tracks under the tree from any terminal. * New: In Etesian::Area, Slice and SubSlice, add support for track avoidance. Exported to the Python wrapper. * New: SubSlice::getUsedVTracks() to get a set of tracks blocked by the cell. * New: SubSlice::trackAvoid(), shift left/rigth the cell under the requested vertical track. Try only to move the cell under the track and not it's neighbor, so it assume that there is sufficient space left or right of the cell. * Bug: In cumulus/plugins.block.configuration.BlockConf, the Cfg parameters may be read too early from the Cfg space into the various sub-conf objects (like FeedsConf). Delay the reading of the parameters in a _postInit() functions. Modify Block and CoreToChip to call _postInit(). * New: In cumulus/plugins.block.configuration.BlockConf._loadRoutingGauge, allow the cell gauge name to differ from the routing gauge name. * New: In cumulus/plugins.block.configuration.FeedsConf, allow to select the default feed to be used with 'etesian.defaultFeed' parameter. * New: In cumulus/plugins.block.spares.BufferPool, allow to control whether or not we want tie to either side of the pool. (for latch up). * New: In cumulus/plugins.block.HTree._connectLeaf(), add support for track avoidance. * Bug: In cumulus/plugins.block.HTree._connectLeaf(), the TL2 contact, the one on the *top* auxiliary buffer seemed to have been badly positioned until now (too low, not using tl2Y). This is strange because it should have caused disconnections, but I didn't see it in the wiring and the regressions tests didn't flag anything wrong. Still a bit weird and worrying.
2022-12-13 09:02:23 -06:00
AutoSegment::create( currTerm , currContact, Flags::Vertical );
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
AutoSegment::create( prevContact, currContact, Flags::Horizontal );
}
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderHybridVH::_do_xG_xM1_xM3 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_xG_xM1()" << endl;
sortRpByX( getRoutingPads(), NoFlags ); // increasing X.
doRp_xG_xM1_xM3( getRoutingPads() );
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderHybridVH::_do_1G_xM1 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_1G_xM1()" << endl;
if (getConnexity().fields.M1 == 1)
_do_xG_1M1();
else
_do_xG_xM1_xM3();
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderHybridVH::_do_xG ()
{
cdebug_log(145,1) << getTypeName() << "::_do_xG()" << endl;
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
const Layer* viaLayer = Session::getBuildContactLayer( 0 );
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
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 NetBuilderHybridVH::_do_1G_1PinM1 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_1G_1PinM1() [Managed Configuration - Optimized] " << getTopology() << endl;
AutoContact* rpContact = doRp_AccessNorthSouthPin( getGCell(), getRoutingPads()[0] );
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
AutoContact* turn1 = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( rpContact, turn1, Flags::Vertical );
if (north() or south()) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
AutoContact* turn2 = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( turn1, turn2, Flags::Horizontal );
turn1 = turn2;
}
setBothCornerContacts( turn1 );
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderHybridVH::_do_2G_1PinM1 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_2G_1PinM1() [Managed Configuration - Optimized] " << getTopology() << endl;
AutoContact* rpContact = doRp_AccessNorthSouthPin( getGCell(), getRoutingPads()[0] );
AutoContact* tee = nullptr;
if (east() and west()) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
tee = AutoContactHTee::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
} else {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
tee = AutoContactVTee::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
}
AutoSegment::create( rpContact, tee, Flags::Vertical );
setBothCornerContacts( tee );
cdebug_tabw(145,-1);
return true;
}
Support for avoidance of vertical tracks in low metal techs. * New: In NetBuilderHybridVH::_do_1G_xM1_1PinM1(), added configuration to manage pins on the north/south sides for VH,2RL. * Bug: In NetBuilderHybridVH::doRp_xG_xM1_xM3(), correct misplaced vertical creation (buildind invalid topologies). * New: EtesianEngine::toColoquinte(), display histograms of the cells widths (in pitch) before and after bloating to get a better feeling of the behavior. * New: In EtesianEngine, add support for track avoidance. Portions of tracks to avoid are specified by a Box, which should flat and on the axis of the request track. This feature is used by the H-Tree to clear the vertical tracks under the tree from any terminal. * New: In Etesian::Area, Slice and SubSlice, add support for track avoidance. Exported to the Python wrapper. * New: SubSlice::getUsedVTracks() to get a set of tracks blocked by the cell. * New: SubSlice::trackAvoid(), shift left/rigth the cell under the requested vertical track. Try only to move the cell under the track and not it's neighbor, so it assume that there is sufficient space left or right of the cell. * Bug: In cumulus/plugins.block.configuration.BlockConf, the Cfg parameters may be read too early from the Cfg space into the various sub-conf objects (like FeedsConf). Delay the reading of the parameters in a _postInit() functions. Modify Block and CoreToChip to call _postInit(). * New: In cumulus/plugins.block.configuration.BlockConf._loadRoutingGauge, allow the cell gauge name to differ from the routing gauge name. * New: In cumulus/plugins.block.configuration.FeedsConf, allow to select the default feed to be used with 'etesian.defaultFeed' parameter. * New: In cumulus/plugins.block.spares.BufferPool, allow to control whether or not we want tie to either side of the pool. (for latch up). * New: In cumulus/plugins.block.HTree._connectLeaf(), add support for track avoidance. * Bug: In cumulus/plugins.block.HTree._connectLeaf(), the TL2 contact, the one on the *top* auxiliary buffer seemed to have been badly positioned until now (too low, not using tl2Y). This is strange because it should have caused disconnections, but I didn't see it in the wiring and the regressions tests didn't flag anything wrong. Still a bit weird and worrying.
2022-12-13 09:02:23 -06:00
bool NetBuilderHybridVH::_do_1G_xM1_1PinM1 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_1G_xM1_1PinM1() [Managed Configuration - Optimized] " << getTopology() << endl;
sortRpByX( getRoutingPads(), NoFlags ); // increasing X.
vector<RoutingPad*> rpsM1;
RoutingPad* rpM2 = nullptr;
for ( RoutingPad* rp : getRoutingPads() ) {
if (dynamic_cast<Pin*>(rp->getOccurrence().getEntity())) rpM2 = rp;
else rpsM1.push_back( rp );
}
if (rpsM1.size() > 1)
doRp_xG_xM1_xM3( rpsM1 );
else
doRp_xG_1M1( rpsM1[0] );
AutoContact* rpContact = doRp_AccessNorthSouthPin( getGCell(), rpM2 );
AutoContact* rpM1Contact = doRp_Access( getGCell(), rpsM1.front(), NoFlags );
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
AutoContact* turn1 = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
AutoContact* turn2 = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
Support for avoidance of vertical tracks in low metal techs. * New: In NetBuilderHybridVH::_do_1G_xM1_1PinM1(), added configuration to manage pins on the north/south sides for VH,2RL. * Bug: In NetBuilderHybridVH::doRp_xG_xM1_xM3(), correct misplaced vertical creation (buildind invalid topologies). * New: EtesianEngine::toColoquinte(), display histograms of the cells widths (in pitch) before and after bloating to get a better feeling of the behavior. * New: In EtesianEngine, add support for track avoidance. Portions of tracks to avoid are specified by a Box, which should flat and on the axis of the request track. This feature is used by the H-Tree to clear the vertical tracks under the tree from any terminal. * New: In Etesian::Area, Slice and SubSlice, add support for track avoidance. Exported to the Python wrapper. * New: SubSlice::getUsedVTracks() to get a set of tracks blocked by the cell. * New: SubSlice::trackAvoid(), shift left/rigth the cell under the requested vertical track. Try only to move the cell under the track and not it's neighbor, so it assume that there is sufficient space left or right of the cell. * Bug: In cumulus/plugins.block.configuration.BlockConf, the Cfg parameters may be read too early from the Cfg space into the various sub-conf objects (like FeedsConf). Delay the reading of the parameters in a _postInit() functions. Modify Block and CoreToChip to call _postInit(). * New: In cumulus/plugins.block.configuration.BlockConf._loadRoutingGauge, allow the cell gauge name to differ from the routing gauge name. * New: In cumulus/plugins.block.configuration.FeedsConf, allow to select the default feed to be used with 'etesian.defaultFeed' parameter. * New: In cumulus/plugins.block.spares.BufferPool, allow to control whether or not we want tie to either side of the pool. (for latch up). * New: In cumulus/plugins.block.HTree._connectLeaf(), add support for track avoidance. * Bug: In cumulus/plugins.block.HTree._connectLeaf(), the TL2 contact, the one on the *top* auxiliary buffer seemed to have been badly positioned until now (too low, not using tl2Y). This is strange because it should have caused disconnections, but I didn't see it in the wiring and the regressions tests didn't flag anything wrong. Still a bit weird and worrying.
2022-12-13 09:02:23 -06:00
AutoSegment::create( rpM1Contact, turn1, Flags::Vertical );
AutoSegment::create( rpContact , turn2, Flags::Vertical );
AutoSegment::create( turn1 , turn2, Flags::Horizontal );
cdebug_tabw(145,-1);
return true;
}
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
bool NetBuilderHybridVH::doRp_1G_1PinM2 ( RoutingPad* rp )
{
cdebug_log(145,1) << getTypeName() << "::doRp_1G_1PinM2() [Managed Configuration - Optimized] " << getTopology() << endl;
AutoContact* rpContact = doRp_AccessEastWestPin( getGCell(), rp );
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
AutoContact* turn1 = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( rpContact, turn1, Flags::Horizontal );
if (east() or west()) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
AutoContact* turn2 = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( turn1, turn2, Flags::Vertical );
turn1 = turn2;
}
setBothCornerContacts( turn1 );
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderHybridVH::_do_1G_1PinM2 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_1G_1PinM2() [Managed Configuration - Optimized] " << getTopology() << endl;
doRp_1G_1PinM2( getRoutingPads()[0] );
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderHybridVH::_do_xG_1PinM2 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_xG_1PinM2()" << endl;
AutoContact* rpContact = doRp_AccessEastWestPin( getGCell(), getRoutingPads()[0] );
AutoContact* neContact = nullptr;
AutoContact* swContact = nullptr;
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
const Layer* viaLayer = Session::getBuildContactLayer( 0 );
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
if (getConnexity().fields.globals == 2) {
if (north() and south())
neContact = AutoContactVTee::create( getGCell(), getNet(), viaLayer );
else
neContact = AutoContactHTee::create( getGCell(), getNet(), viaLayer );
AutoSegment::create( rpContact, neContact, Flags::Horizontal );
setBothCornerContacts( neContact );
} else if (getConnexity().fields.globals == 3) {
swContact = AutoContactVTee::create( getGCell(), getNet(), viaLayer );
neContact = AutoContactVTee::create( getGCell(), getNet(), viaLayer );
if (west())
AutoSegment::create( rpContact, neContact, Flags::Horizontal );
else
AutoSegment::create( rpContact, swContact, Flags::Horizontal );
AutoSegment::create( swContact, neContact, Flags::Vertical );
setNorthEastContact( neContact );
setSouthWestContact( swContact );
}
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderHybridVH::_do_1G_xM1_1PinM2 ()
{
cdebug_log(145,1) << getTypeName() << "::_do_1G_xM1_1PinM2() [Managed Configuration - Optimized] " << getTopology() << endl;
sortRpByX( getRoutingPads(), NoFlags ); // increasing X.
vector<RoutingPad*> rpsM1;
RoutingPad* rpM2 = nullptr;
for ( RoutingPad* rp : getRoutingPads() ) {
if (dynamic_cast<Pin*>(rp->getOccurrence().getEntity())) rpM2 = rp;
else rpsM1.push_back( rp );
}
if (rpsM1.size() > 1)
doRp_xG_xM1_xM3( rpsM1 );
else
doRp_xG_1M1( rpsM1[0] );
Pin* pin = dynamic_cast<Pin*>( rpM2->getOccurrence().getEntity() );
Pin::AccessDirection pinDir = pin->getAccessDirection();
AutoContact* rpContact = doRp_AccessEastWestPin( getGCell(), rpM2 );
AutoContact* rpM1Contact = nullptr;
if (pinDir == Pin::AccessDirection::EAST)
rpM1Contact = doRp_Access( getGCell(), rpsM1.back(), NoFlags );
else
rpM1Contact = doRp_Access( getGCell(), rpsM1.front(), NoFlags );
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
AutoContact* turn = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( rpM1Contact, turn, Flags::Vertical );
AutoSegment::create( rpContact , turn, Flags::Horizontal );
cdebug_tabw(145,-1);
return true;
}
bool NetBuilderHybridVH::_do_1G_1M1 () { return false; }
// bool NetBuilderHybridVH::_do_xG_1Pad () { return false; }
// bool NetBuilderHybridVH::_do_xG_xM2 () { return false; }
// bool NetBuilderHybridVH::_do_1G_1M3 () { return false; }
// bool NetBuilderHybridVH::_do_xG_xM3 () { return false; }
// bool NetBuilderHybridVH::_do_xG_1M1_1M2 () { return false; }
// bool NetBuilderHybridVH::_do_4G_1M2 () { return false; }
bool NetBuilderHybridVH::_do_2G () { return false; }
bool NetBuilderHybridVH::_do_globalSegment ()
{
cdebug_log(145,1) << getTypeName() << "::_do_globalSegment()" << endl;
cdebug_log(145,0) << "getSourceFlags():" << getSourceFlags()
<< " getFlags():" << getFlags() << endl;
if (getSourceContact()) {
uint64_t segmentBound = getSegmentHookType( getFromHook() );
AutoContact* targetContact
= (segmentBound & (NorthBound|EastBound)) ? getNorthEastContact() : getSouthWestContact() ;
if (not getFromHook()) cerr << "getFromHook() is NULL !" << endl;
AutoContact* sourceContact = getSourceContact();
if (segmentBound & (NorthBound|SouthBound)) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
AutoContact* turn = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( sourceContact, turn, Flags::Vertical );
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
sourceContact = AutoContactTurn::create( getGCell(), getNet(), Session::getBuildContactLayer(0) );
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
AutoSegment::create( sourceContact, turn, Flags::Horizontal );
}
Segment* baseSegment = static_cast<Segment*>( getFromHook()->getComponent() );
AutoSegment* globalSegment = AutoSegment::create( sourceContact
, targetContact
, baseSegment
);
globalSegment->setFlags( (getDegree() == 2) ? AutoSegment::SegBipoint : 0 );
cdebug_log(145,0) << "Create global segment: " << globalSegment << endl;
// HARDCODED VALUE.
if ( (getTopology() & Global_Fixed) and (globalSegment->getAnchoredLength() < 2*Session::getSliceHeight()) )
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 NetBuilderHybridVH::singleGCell ( AnabaticEngine* anbt, Net* net )
{
cdebug_log(145,1) << getTypeName() << "::singleGCell() " << net << endl;
vector<RoutingPad*> rps;
for ( RoutingPad* irp : net->getRoutingPads() )
rps.push_back( irp );
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;
}
sortRpByX( rps, NetBuilder::NoFlags ); // increasing X.
GCell* gcell1 = anbt->getGCellUnder( rps.front()->getCenter() );
GCell* gcell2 = anbt->getGCellUnder( rps.back ()->getCenter() );
if (not gcell1) {
cerr << Error( "No GCell under %s.", getString(rps.front()).c_str() ) << endl;
cdebug_tabw(145,-1);
return;
}
if (gcell1 != gcell2) {
cerr << Error( "Not under a single GCell %s.", getString(rps.back()).c_str() ) << endl;
cdebug_tabw(145,-1);
return;
}
AutoContact* prevContact = nullptr;
AutoContact* currContact = nullptr;
for ( size_t i=0 ; i<rps.size() ; ++i ) {
prevContact = currContact;
AutoContact* currTerm = doRp_Access( gcell1, rps[i], NoFlags );
if (i == 0) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
currContact = AutoContactTurn::create( gcell1, net, Session::getBuildContactLayer(0) );
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
AutoSegment::create( currTerm, currContact, Flags::Vertical );
continue;
}
if (i+1 == rps.size()) {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
currContact = AutoContactTurn::create( gcell1, net, Session::getBuildContactLayer(0) );
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
} else {
Extend routing gauge to support non-routing layers at the bottom. * New: In CRL::RoutingLayerGauge, two new types of gauge are supported: - Unusable : just do nothing with it, but the layer is stacked. - BottomPowersupply : can be used for supply routing only, and is *below* the normal routing layers (instead of on top as usual). Both new types must be *below* the real routing layers. * New: In CRL::RoutingGauge, add a new attribute "firstRoutingLayer" to give the index (depth) of the first layer usable for routing. (not Unusable and not BottomPowerSupply) * New: In Anabatic::Session & Anabatic::NetBuilder, in order to build the initial wiring, provides (Session) and use (NetBuilder) the new functions: - getBuildRoutingLayer(depth) - getBuildContactLayer(depth) Thoses functions takes into account (offset) the unusable layers so depth 0 is the first usable routing layer, and so on.
2023-01-07 05:51:38 -06:00
currContact = AutoContactHTee::create( gcell1, net, Session::getBuildContactLayer(0) );
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
}
AutoSegment::create( currTerm , currContact, Flags::Vertical );
AutoSegment::create( prevContact, currContact, Flags::Horizontal );
}
cdebug_tabw(145,-1);
}
string NetBuilderHybridVH::getTypeName () const
{ return "NetBuilderHybridVH"; }
} // Anabatic namespace.