The file of the register channel, laid out #
DescriptiveComplexity.Draw.Data.diagLaid reads the segment channel's ruler
as a DescriptiveComplexity.Draw.LaidFile: one register per element of the
universe, in the universe's own order, each naming its own tag's block and its
own tuple. This file does the same for the register channel, whose file has
one register per element the channel writes for.
Everything the evaluation asks of a layout is the elementwise one's, restricted:
- a register is an element, so the block and the named coordinates spell it
(
nameSep_regLaid); - every block and named tuple has a register, provided the reduction writes for
the argument elements – which is what it does, and what makes its file lie in
the working region (
hasName_regLaid); - the registers grow with the elements (
wmSetLt_wmRegSeg), which is the one property the singleton channel could not give.
The index of the register channel's file: the elements it writes for.
Equations
- dt.RegIx = { x : DescriptiveComplexity.Draw.Univ A R' P' dt.KIx dt.dd // DescriptiveComplexity.WMHasInp x }
Instances For
Dependency graph
The register channel's file, laid out: one register per element the channel writes for, in the universe's own order, each naming its own tag's block and its own tuple.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Dependency graph
The file has a register for every name, provided the channel writes for
the argument elements: a register is an element, and a name is one of them. This
is the one thing the reduction has to arrange about its channel, and arranging
it is what puts the file in the working region – the argument tags are the
greatest (DescriptiveComplexity.Draw.lt_arg).
Dependency graph
The coherences the evaluation asks of a file #
A named register stands for the element it names: the heltP
coherence.
Dependency graph
What the file costs to walk #
The number the register channel's walks are charged against: 2 ^ the
number of registers, which is the size of the working region and the bound every
address of the file is under.
Instances For
Dependency graph
The width a walk to a register is charged: twice the bound, plus two.
Instances For
Dependency graph
The width of the pass over the whole file: the file's two ends, the walk between them at one bound a step, and the marker's own address.
Instances For
Dependency graph
The width of a read below the file: an address under the first register is under the bound.
Instances For
Dependency graph
The width of a stage's inner loop: a pass per bit of the address it
carries, each pass priced as regWP.
Equations
- One or more equations did not get rendered due to their size.