Documentation

Complexity.Algorithms.WordRAM.MatrixMultiplication.Schonhage.Wanted.Memory

Concrete memory layout of native wanted-query grouping #

Main definitions #

All layout definitions are numeric specifications of actual address instructions. Neither the layout nor the parameter record contains a run, time bound or assumed solver.

The original length word, four headers and two words per wanted position.

Instances For

    The forward table follows a complete 2^L-word inverse table.

    Instances For

      Tile counts follow both computed tables.

      Instances For

        One immutable prefix offset per tile, followed by one terminal offset.

        Instances For

          Mutable stable-scatter cursors follow the immutable prefix offsets.

          Instances For

            One actual query code per original occurrence.

            Instances For

              Every code retains its original input position in the adjacent array.

              Instances For

                One past both grouped output arrays.

                Instances For

                  This sufficient budget covers the reused parameter kernels as well as all routing and grouping arithmetic. It depends only on the original four scalar parameters.

                  Instances For

                    Persistent scalar register values after actual table relocation and allocation.

                    Instances For

                      The exact scalar register footprint shared by the grouping passes.

                      Instances For

                        Persistent scalar contracts survive preservation of their concrete registers.