* Change: In Anabatic::Autocontact, replace getMinDepth() and
getMaxDepth() by getDepthSpan().
* New: In Anabatic::AutoSegment::canMoveUp(), add an optional check of
low up density (Flags::CheckLowUpDensity). Allows to move up a
segment if the up density is (very) low, and in this case it's more
efficient than breaking it to fit in the lower layer.
canMoveUp() is now able to perform the same work as canPivotUp()
if *not* supplied the flag Flags::IgnoreContacts.
* New: In Katana, in GlobalRouting::DigitalDistance() now take into
account the cost of a VIA (currently set to 2.5). Need to known the
Net currently routed in the DigitalDistance object itself.
* Change: In Katana::Track::Element::canPivotUp(), now also takes a flag
parameter.
* Change: In Katana::Manipulator, new flag IgnoreContacts to mirror the
one of Anabatic.
* Change: In Katana::SegmentFsm, allocate once a Manipulator object instead
of many times on the fly.
In SegmentFsm::_slackenGlobal(), in the slacken state, if the up
density is (very) low, bypass to move up instead of slackening.
This solve better the routing of the control part of the register file.
The register file having a pathological case of terminal placement:
many punctual terminals aligneds in METAL2 *and* a grid of METAL2 and
METAL3 blockages near below...
* Bug: In Katana::Session::_revalidate(), after removing the zero-length
segments, forgot to re-order the track, leading to many stranges effects
as the indexes where no longer coherent in the Track.
* Change: In PyHurricane.h, in HCATCH macro, show the backtrace when
catching a C++ exception. No need to use the "hex" stream manipulator
if we cast into (void*).
* Bug: In Cumulus & Stratus, now that creation of Hurricane objects must be
enclosed in UpdateSession, has to adds them into Python code.
* Bug: In Anabatic & Katana, in the global routing stage suspend the timed
bewteen ripup steps instead of resetting it.
* Bug: In Anabatic::RawGCellsUnder, *again*, the north and east borders
of the whole area *are* includeds (shut up disgraceful warning).
* New: In Anabatic::GCell, add a display mode to select between boundary
display (for analogic) and density display (for numeric).
* Bug: In KatanaEngine::runGlobalRouter(), do not check if an Edge cannot
be desatured when the vector or overloaded Edges is empty.
(one less disgraceful warning)
* New: In GraphicKatanaEngine::drawGCell(), support for drawing the GCells
in density mode. Use the fire scale and the MaxDensity mode.
Setup the GCell drawing mode in GraphicKatanaEngine::initGCell().
* Change: In GraphicKatanaEngine::drawEdge(), adjust the various thresholds
for showing the Edge and its label.
* New: In CRL Core, adds "anabatic.gcell.displayMode" to the set of Anabatic
parameters.
Adjust the showing threshold for GCells in "display.conf" so when the
zoom level is low, we still can see the density map.
* New: In Hurricane::UpdateSession, added "reset()" static function to
close all the currently opened sessions.
* New: In Hurricane::ExceptionWidget::catchAllwrapper(), close all
pending UpdateSession if the user choose to resume.
* Change: In Hurricane::Go, instead of immediatly materializing a newly
created Go (inserting it in a QuadTree) delay it until the closing
of the UpdateSession. We call "invalidate()" in "_postCreate()"
instead of "materialize()". This way, the abutment box of Gos is
taken into account only when the session is closed. There was a
problem when the abutment box was changing after the object creation
misleading the algorithm of the QuadTree. This was occuring only
when an object was created, not modificated, because in the later case
the Session mechanism was used. Now, the Session mechanism is used
in all cases.
As a side effect, it will speed up the parser by making all QuadTree
insertions in one step.
* Change: In Hurricane::JsonCell, forgot to call Cell::materialize() when
the Cell is completed (as was done in ordinary parsers). The call is
made in the destructor of the JsonCell.
* Change: In Hurricane::Cell, add QuadTree in the inspector support.
* Change: In Anabatic, remove GraphicAnabaticEngine, PyGraphicAnabaticEngine,
PyAnabaticEngine (but keep PyAnabatic for constants exportation)
and GlobalRoute (moved to Katana). Drawing methods for Edge & GCell
are moved into GraphicKatanaEngine.
* Bug: In Anabatic, in AutoHorizontal & AutoVertical, native constraints
must use GCell::getConstraintsUMax().
* Bug: In Anabatic::GCell, correct terribly bad implementation of
both getConstraintUmax().
In getSide(), use getConstraintUMax().
* Bug: In Anabatic::AutoContact, setCBUMax() must be set using the GCell
getContraintUMax().
* New: In PyAnabatic, export the various Engine constants.
* Change: In Katana, in TrackElement and derived classes, add a getSegment()
method for easier access to the underlying Hurricane segment.
* New: In PyKatanaEngine, export the loadGlobalRouting method which was
missing (for use by Unicorn/cgt).
* Bug: In Dijkstra::_materialize(), in some special case a connex component
can is reached by two (or more) vertexes. But of course it will be
connected only through one, all others must be discarteds. The right
one will have it's connex id set, all the others will stay to -1.
So stop any backtrack when the first neighbor of a starting point
has it's connex id *not* set.
* Bug: In Anabatic::GCell, new functions getConstraintUMax() to return the
correct bounding box for the last north/east GCell. The GCells do not
own their north/east edges, except for the last ones. Thoses functions
must distinct from getUMax() because for them, the shrink is always
applied. getConstraintBox() uses the "getConstraintUMax()" functions.
* Bug: In Anabatic::AutoContact, initialize the constraint box from the
new GCell::getConstraintUMax(), to manage correctly the boundaries
of the nothernmost & easternmost GCells. The problem was showing for
pins on the north/east side of a circuit, the constraint
* Bug: In Anabatic::AutoContactHTee, Anabatic::AutoContactVTee and
Anabatic::AutoContactTerminal forgot to call the _preCreate() function
in the various create().
* Bug: In Matrix::getUnder(), if on the N/E boundary, decrease by one to
be enclosed in it.
- Modified: Matrix is now correctly updated for irregular floorplans.
Dijkstra:
- Modified: Source and Target contacts are now correctly chosen in _materialize.
* Bug: In Hurricane, in StaticObservable::getObserver(), if the slot
pointer is NULL, do not try to access the owner. Returns NULL, so
the caller can be aware of the situation...
* Change: In Hurricane, in BreakpointWidget & ExceptionWidget some
cosmetic changes (fonts and window sizes).
* Bug: In Anabatic, In AutoHorizontal::getConstraints(), take into account
the constraints from the source AutoContact, as it holds the constraints
transmitted by the RoutingPads and sets up by propageConstraintsFromRp().
It is likely to be a bug affecting the original Katabatic as well.
* Change: In Anabatic, in RawGCellsUnder(), check that the segment is not
completly oustside the cell abutment box and truncate the coordinates
to the part that is inside. Use the "shrink" if we reach the east/north
border.
* Change: In Anabatic, in Configuration, no more decorator because we will
use a true derived relationship. Katana *derives* from *Anabatic* and do
not *decorate* it, so the Configuration can do the same. It also implies
that we directly create a Katana engine, not an Anabatic one.
* Change: In Anabatic, in Session, do not allow the opening of the Session
in a standalone fashion (with a static method). Instead it must be opened
using the relevant method of the Anabatic/Katana engine. This ensure we
are opening the right Session type.
* Change: In Anabatic, in AutoSegment_Aligneds() collection the seed segment
is not part of the collection by default, but will be included if the
Flags::WithSelf is set.
* Change: In Configuration, all the flags value are now defined in two steps.
Declared in the header and initialized in the module. This is to prevent
the fact that on some cases, in relation with the Python "extern C" part
modules, we need a true allocated variable. It was causing weird linking
problems.
A side effect is that they can no longer be used as entry is switches,
have to replace them by if/else.
* New: In Anabatic, new GCell::getNeighborAt() utility function.
* Bug: In Anabatic, in GCell::doGrid(), tag all the GCells of the grid with
the grid type... Back annote all the edges capacity (north & east) with
the reserved local capacity.
* New: Complete portage of Kite over Anabatic. The new engine is christened
"Katana" for Kite-Analogic. When it's capabilities and performances
will be on a part with Kite, it is to completly replace it (and take
back the "Kite" name). Preliminary tests seems to show that, contrary
to intuition (because built on a more complex/slower grid), it is even
slightly faster than Kite 8-).
* Bug: In Hurricane, in NetlistWidget CTOR, the horizontal header was set
up assuing that there was (at least) three sections (column) in the
model, which was wrong. Now it is done in the setCell() method which
know the exact number of sections.
It was a bug in both Qt 4 & 5, but was showing only under Qt 5.
* Bug: In Hurricane, in Backtrace, under RHEL 6 when the package
<devtoolset-2-binutils-devel> is *not* installed, Backtrace uses the
wrong "bfd.h" from the system instead of the one from the devtoolset2,
causing itself to core.
The Backtrace, then try to create a second Backtrace from this
error, generating an infinite loop. To prevent this situation add a
counter so that only one Backtrace can be created at a any time.
And incidentally display a more meaningful error message along with
* Bug: In Anabatic::GCell, when width and/or heigh is null, do not try to
compute densities as it will trigger a divide by zero (and do not make
much sense anyway).
* Change: In CRL Core, in cmos/alliance.conf, honor the ALLIANCE_TOP variable
if it is found in the user's environement.
* New: In Bootstrap, add cmake detection for libbfd.
* New: In Hurricane, in Backtrace, add BFD support to read debuginfo from
the shared libraries (aka DSO) when compiled with "-g". This avoid the
tedious step of running gdb after generating a core dump. It is also
mandatory in ExceptioWidget to known from where an exception was thrown
as Qt::notify() block all C++ exceptions.
Currently works only under Linux (gcc or clang), may be extended in
the future.
The BFD reading is based on the small utility from:
Don Hatch (hatch@plunk.org)
http://www.plunk.org/~hatch/goodies/backtracefilt.C
And small trinket: adjust the size of the window for high DPI screens.
* New: In CRL Core & Unicorn add link toward libbfd, if needed.
* New: In Anabatic:
- In AnabaticEngine, create a new NetData information for storing
the static ordering of nets (for the global routing). The order
is the half perimeter of the search area divided by the number
of RoutingPads. The order is static once it as been computed in
the first place (even through ripup stages).
* Change: In Anabatic:
- Long wires, going straight accross multiple GCells were splitted
into a long sequence of segment+contact, one for each gone-through
GCell. It was memory-consuming and algorithmically inefficient.
Now there is only one straight wire.
As a consequence, Edges now store the list of all segments
going through them. That way we do not need to load a Net into
Dijkstra before riping up some of it's segment. The ripup mechanims
can now be implemented right at AnabaticEngine level, without
dependencies over Dijkstra. Note that long wires are automatically
broken in two if we need to attach a new branch on it (breakAt()).
And fused back into one if a branch is removed (unify()).
* Bug: In Cumulus, in ClockTree plugin in GaugeConf._rpAccess() do not
create the stack of access VIAs each time the function is called.
Instead maintain a lookup table of the already generated ones.
Was blocking the loading of pre-routed nets in Anabatic.
* Bug: In Hurricane, in tstream (Commons.h), in the *template* overload of
operator<<(), do not use the operator<<() of ostream as it will be
looked up in "stage 1" (template definition) and so will miss all the
overloads added later and built over getString<>(). Instead, make use
of getString<>(), which, as another template will be looked up in
"stage 2" (template instanciation) and at that point will have all the
needed template specialisation of getString<>().
We also need to define new stream manipulators to be able to create
a matching template overload not dependant from the implementation.
To avoid name clashes, we prefix a 't'. For now, only 'tsetw()' is
refined.
As a side effect, we cannot directly print bit-fields into the stream,
we must go through an intermediate variable (happens once in AutoContact).
Jean-Paul Chaput
EricLaoGitHub
Roselyne Chotin-Avot