- Change: In KatabaticEngine, the containers used to store the "nets to
route" is changed from a vector<> to a set<> sorted by the Nets names.
Uses more memory but allows much faster Net deletion.
- New: In _loadNetGlobalRouting(Net*), detect non-routed Nets. A Net is
considered as unrouted if it's 10 first RoutingPads have no slave
Segment. The Net is withdrawn from the set of Nets to route.
- Bug: In GCellConfiguration::_GCell_1G_1L1(), correctly compute the
access flag passed to _GCell_rp_Access().
- Change: In AutoContact::restrictConstraintBox() adds "warnOnError"
parameter to shut down warnings.
- New: KatabaticEngine::_computeNetConstraints() now also returns a set<>
of segments on which constraints are incompatibles. All the NetConstraints
related functions are modificateds accordingly.
- Change: In KatabaticEngine::_loadNetGlobalRouting(), create dogleg
on overconstrained Segments computed by a call to _computeNetConstraints().
Overconstraineds Segments can occurs when a global is directly
connecting two punctual RoutingPads (see "ieee_division").
As a side effect, and to avoid looping each Net is revalidated
*before* making any dogleg. So Nets are revalidated one by one instead
of alltogether.
- Change: In AutoSegment::_toConstraintAxis(), do nothing if constraint
interval is empty.
- Change: In KnikEngine::initGlobalRouting(), increase the maximal degree
of net to be routed (1000 -> 13000). This to allow the clock to be
routed of the "vld" circuit.
- Bug: In Net.h, force expansion of SlotTemplate<Net*> with the line:
const SlotTemplate<Net*> dummyNetSlot ( string("dummyNetSlot"), NULL );
I've no satisfactory explanation, but in the cyclop Inspector the
Cell's NetMap is correctly created and in the cgt Inspector, Nets
entries of the NetMap appears as "unsupported", meaning that the
SlotTemplate<> has not been generated for Net. This correct the
problem.
- Change: In TrackCost, the ripup cost is now computed from a mix between
the number of ripup *and* the data state. Restore a correct balance
of the ripping up between segments.
- New: In RoutingEvent::State::conflictSolve1(), when a very long Segment
enters in conflictSolve1(), still prefers to move it up in one piece,
but if it's not possible, it is unlikely that it will overlap with
only one or two other Segment. In that cases, blindy break it up in
the middle.
- New: In RoutingEvent::Manipulator, another overload of makeDogLeg to
allow break up at one precise point.
- Change/Bug: In RoutingEvent::Manipulator::Relax(), reset the state of
the non-overlapping Segment fragments instead of inheriting blindly
of the state of the breaked up one. Gives some supplemental slack
that allows to converge.
- Note: Now the strategy is to disable the uses of GCellRoutingSet by
setting the expand step to 0.99. This induces only a slight slow
dow and memory increase and passes all the tests...
- Mark: This revision passes all the benches except for idct, vld &
ieee_division.
- Bug: In KatabaticEnginge::_desaturate() (part of LayerAssign), reset
the moved up Segment pointer between iterations. Suppress the warning
about the GCell's DyKeyQueue beeing not revalidated on deletion.
- Change: In LoadGrByNet, manage the 4G+3L1 configuration with the generic
_GCell_xG_xL1_xL3(). Needed for "dct_lvl2".
- Bug: In top CMakeLists.txt the SETUP_PROJECT_PATHS was not inserting
X_USER_TOP *before* X_TOP, thus potentially allowing an obsolete
system-wide configuration to shadow an up-to-date local one.
* ./unicorn:
- New: "--show-conf" options to dump the current configuration.
- Bug: In top CMakeLists.txt the SETUP_PROJECT_PATHS was not inserting
X_USER_TOP *before* X_TOP, thus potentially allowing an obsolete
system-wide configuration to shadow an up-to-date local one.
- Bug: In top CMakeLists.txt the SETUP_PROJECT_PATHS was not inserting
X_USER_TOP *before* X_TOP, thus potentially allowing an obsolete
system-wide configuration to shadow an up-to-date local one.
- Bug: In top CMakeLists.txt the SETUP_PROJECT_PATHS was not inserting
X_USER_TOP *before* X_TOP, thus potentially allowing an obsolete
system-wide configuration to shadow an up-to-date local one.
* ./kite:
- Change: In Configuration/KiteEngine, propagate changes in Configuration
in Kite. Note that a *second* singleton is created at Kite level.
- New: KiteEngine::printConfiguration() method to allow quick checks of
the router's main parameters.
- New: ConfigurationWidget to display/sets all the revelant Katabatic/
Kite configuration parameters. To be used with the TabSettings from
the ControllerWidget.
The ConfigurationWidget is bound to the default (static) Kite
configuration, as once it has been run you obviously cannot change the
router's settings.
- Bug: In top CMakeLists.txt the SETUP_PROJECT_PATHS was not inserting
X_USER_TOP *before* X_TOP, thus potentially allowing an obsolete
system-wide configuration to shadow an up-to-date local one.
* ./katabatic:
- Change: In Configuration/KatabaticEngine, introduce a static Configuration
object (singleton) to handle the default configuration. Configuration are
now created only through cloning operations. In KatabaticEngine, the
_configuration becomes a pointer (previoulsy an value).
Confifuration becames a singleton and a decorator.
Also adds a print method to nicely display configurations values on
the terminal.
- Bug: In top CMakeLists.txt the SETUP_PROJECT_PATHS was not inserting
X_USER_TOP *before* X_TOP, thus potentially allowing an obsolete
system-wide configuration to shadow an up-to-date local one.
* ./knik:
- Bug: In MatrixVertex, still the same index bug problem (incomplete
correction).
- Bug: In top CMakeLists.txt the SETUP_PROJECT_PATHS was not inserting
X_USER_TOP *before* X_TOP, thus potentially allowing an obsolete
system-wide configuration to shadow an up-to-date local one.
* ./crlcore:
- New: In Utilities, The Dots class which allow nice pretty printing on
a terminal (like lines of books summaries).
- Bug: In CellWidget, correct the slightly off position of Labels references.
- New: In ControllerWidget, new TabSettings tab to hold the configuration
settings of the various Coriolis tools. The TabSettings is a tab itself.
- New: In buildCoriolis.py, adds a "--rm-build" option which removes the
tool's build directory before building it. A very crude way to ensure
that nothing obsolete form a previous build will gets in the way...
- Bug: In PaletteWidget, do not derive from QScrollArea. Instead uses it
as a child widget. This solves the refreshing problem of the Palette.
As a rule now: never derives from anything other than QWidget.
- New: GotoWidget, not having this feature finally unverved me enough for
beeing implemented. You can specify an (x,y) on which the view will
be centered and an aperture which gives the size of the view smallest
side. It's a way of specifying the zoom level (as the zoom is not
meaningful for users). An aperture of "zero" disable that feature,
that is, zoom remains unchanged. The coordinates are integer which
are implicitly expressed in the current mode used by the viewer
(Symbolic, Grid, or Physical in micro-meters).
- Change: Big rewrite of how the Symbolic/Grid/Physical modes are sets
to/from the CellWidget. Impacted widgets are CellWidget &
DisplayFilterWidget.
Main changes are that there is no more "individual" setter/getter for
modes (setSymbolic(), setGrid(), setPhysical(DbU::UnitPower)) but one
with two arguments:
setDbuMode(int mode,DbU::UnitPower)
Signals & slots of the widgets also evolves into:
dbuModeChanged(int mode,DbU::UnitPower)
changeDbuMode (int mode,DbU::UnitPower)
- Change: In TrackFixedSegment, when the source/target coordinates of the
fixed segment are outside the grid (i.e. the Cell Abutment Box) truncate
them.
- Change: In GCell::addTrackSegment, when looking for overlap between the
to be inserted TrackSegment and Blockage segment, shrink the Blockage
span by one DbU to avoid false overlap when they are just edges connexes.
- Bug: In RoutingEvent::slackenTopology, in the local segment FSM, looping
on the MaximumSlack state. Now also checks the state count.
- Change: In TrackSegment::canMoveUp() & canPivotUp() adds the "reserve"
parameter and uses it in RoutingEvent to prevent over saturated GCells.
- Change: In Configuration, parameters adjustements: expandStep increased to
0.40. Makes RoutingSets biggers but no noticeable slow down.
- Change: In Grid/BaseGrid, add an Abutment Box attribute (to facilitate
segment truncation in Kite::TrackFixedSegment.
- Change: In Grid/BaseGrid::Axis, when computing a row/column index using
the graduation table, if the coordinate is exactly on the last
graduation, return the last GCell instead of "out of bound".
- Change: In GCell::hasFreeTrack(), AutoSegment::canMoveUp() &
AutoSegment::canPivotUp() adds a "reserve" parameter to modify the
amount of wirelength to remains free after the insertion.
- Bug: In MatrixVertex::getLineIndex() and getColumnIndex(), in regular
mode, when the Y/X coordinate is exactly on the upper right angle,
return the inferior index (instead of superior which is out of bounds).
- Change: In MatrixVertex, RoutingGrid & KnikEngine, replace the _lowerLeftX &
_lowerLeftY by a complete copy of the Cell's abutment box. Makes
easier for getLineIndex() to find out of bound coordinates.
- Change: In KnikEngine & LoadSolution add a time/memory measurement,
for Kite statistics.
- New: In AllianceFramework, getInstancesCount() to count the number of
instances in a Cell. The count can be recursive or not or ignore or
not feed cells. This could be viewed as a very simple query, and has
to be implemented here because we only new Feed Cell from the CATAL
of the Alliance Framework.
- Bug: In RoutingEvent::Manipulator::forceToTrack(), wrong return code,
was always return true, blocking the explorations of least good
Track.
- Bug: In RoutingEvent::_processNegociate(), must reset the "insert state"
while looping on candidate. This bug was having the same effect as
(and masking) the previous one!
- Bug: In TrackSegment::moveUp(), reset the ripup count after the move
up...
- Change: At various DebugSession opening points, sets the debug level to
200 to avoid extraneous debugging output.
- New: KiteEngine::dumpMeasures() to create a data file for later uses
by gnuplot. In interactive mode, this function is called in the
"finalize layout" stage.
- New: Adds measurments "algo", "fin" & "Segs".
- Bug: In GCell, bad cast between <size_t> and <unsigned int>, showed only
under 64 bits.
- New: In KatabaticEngine::printMeasures(), adds a support for measurments,
both time and memory size in Mb are stored for each tag.
- New: Adds measurements "Gates", "GCells", "load" & "assign".
- New: The Measure extension (on any DBo) that allows to save measurement
and print them later into a file. Mainly to supply gnuplot with datas.
Obsoletes the "statsExtract.py" script from statistics, and much
more reliable.
- New: In Reference, adds a type to differentiate between "Labels" and
"Position". Labels are strings that we wants to display, and position
are specific points with a name attached to it.
- New: In CellWidget, specific display for the two kind of references
(Label & Display).
- Change: In TrackSegment, _postDogLeg() & _postModify(), add segments to
"Ring" if they are directly connected to a RoutingPad. To maintain the
"border effect" after a topological slackening.
- Change: In GraphicKiteEngine, in the global routing relateds menus, suppress
the mention of "solution" as it might be unclear for an average user.
(just "Save Global Routing" or "Load Global Routing").
- Change: In RoutingEvent, conflictSolve1() tries to move up "other" blocking
segment before trying to break "self".
- Bug: In TrackSegment::reschedule(), remove from Track segments that are
now in a greater order than the current one. This bug was shown in the
TrackSegment::_postModify() method after a desalignate.
It was causing overlaps and/or routing completion false reports.
- New: In GCell & LayerAssign, adds a supplemental desaturation steps when
a GCell containts too many (more than 7) RoutingPads in M1. This is
especially useful for the eFPGA matrix with it's custom made cells.
- Change: In ToolEngine, adds a static method "destroyAll()" that must be
called *before* the Hurricane database destruction. This is to avoid
a mis-oredering in destruction.
ToolEngines are stored in a property, property are part of the DBo
base object so are destroyed *after* the Cell derived object has been.
Thus ToolEngine are deleted *after* the Cell components and if they
still refers to it, we are doomed.
- Change: In display.xml, color support for displaying references.
Jean-Paul Chaput
The Coriolis Project