Merge branch 'feature/latest-dune-richards' into 'master'

See merge request [extensions/dune-codegen!286]

  [extensions/dune-codegen!286]: Noneextensions/dune-codegen/merge_requests/286

Using the same concept we use for visiting with hasattr.

These can be exceptionally challenging while not contributing to the
overall performance. So we might want to skip.

Merge branch 'feature/project-renaming' into 'master'

See merge request [dominic/dune-perftool!283]

  [dominic/dune-perftool!283]: Nonedominic/dune-perftool/merge_requests/283

Hoperfully achieving more robustness w.r.t. submodule changes

Merge branch 'autotune-merge' into 'master'

ref:dominic/dune-perftool Resolving conflicts of [!270]

See merge request [dominic/dune-perftool!282]

  [!270]: gitlab.dune-project.org/NoneNone/merge_requests/270
  [dominic/dune-perftool!282]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/282

Merge branch 'feature/use-custom-geometry-transformation' into 'master'

ref:dominic/dune-perftool This computes the determinant and jacobian inverse
transposed directly within loopy and does not call the corresponding grid
functions. Using some simple precomputations this is faster if
number_of_blocks>=2.

This also allows straight forward vectorization for unstructured grids.

I don't know how the computation of the geometry transformation is done in the
sumfactored case, but maybe there is some overlap, which could be reduced.

See merge request [dominic/dune-perftool!276]

  [dominic/dune-perftool!276]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/276

Merge branch 'feature/skylake-single-precision-transposes' into 'master'

See merge request [dominic/dune-perftool!271]

  [dominic/dune-perftool!271]: Nonedominic/dune-perftool/merge_requests/271

Merge branch 'feature/matrix-inversion' into 'master'

ref:dominic/dune-perftool Matrix inversion at code generation time does only
work to a very limited extent (up to n=4). We can instead assemble the tensor
in C++ and invert it there (e.g. using Dune::FieldMatrix)

This fixes [#123].

Still TODO:

-   \[ \] Vectorized Inversion

See merge request [dominic/dune-perftool!263]

  [#123]: gitlab.dune-project.org/NoneNone/issues/123
  [dominic/dune-perftool!263]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/263


Closes #123

Merge branch 'feature/code-generation-hooks' into 'master'

ref:dominic/dune-perftool This is the first minimal implementation of how code
generation hooks from downstream projects could look like.

There is a few more things to think about (feel invited to share ideas):

-   \[x\] How to document the arguments and return values expected from hooks
-   \[x\] How to handle multiple hooks registered to the same hook point and
    return values (this is quite relevant once you want to do loopy
    transformations in a hook. It means that you want to "chain" the hooks)

This fixes [#129].

See merge request [dominic/dune-perftool!277]

  [#129]: gitlab.dune-project.org/NoneNone/issues/129
  [dominic/dune-perftool!277]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/277


Closes #129

Merge branch 'feature/more-avoiding-of-noop-conditionals' into 'master'

ref:dominic/dune-perftool By looking at the possible values of the condition.

See merge request [dominic/dune-perftool!281]

  [dominic/dune-perftool!281]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/281

By looking at the possible values of the condition.

Merge branch 'feature/avoid-visiting-noop-integrals' into 'master'

ref:dominic/dune-perftool I have a case where visiting has a side effect that
I want to avoid. Also spares work.

See merge request [dominic/dune-perftool!280]

  [dominic/dune-perftool!280]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/280

I have a case where visiting has a side effect that I want to avoid.
Also spares work.

Merge branch 'feature/allow-custom-ufl-types' into 'master'

ref:dominic/dune-perftool We do want code bloat in dune-perftool for the
specific needs of a given application. We therefore allow custom UFL nodes to
procide their own visitor implementation. This was done previously for the
very specific case of a MathFunction node, but it can be done with any node.

See merge request [dominic/dune-perftool!278]

  [dominic/dune-perftool!278]: gitlab.dune-project.org/dominic/dune-perftool/merge_requests/278

Merge branch 'feature/remove-obsolete-argument-from-boundary-predicates' into 'master'

See merge request [dominic/dune-perftool!279]

  [dominic/dune-perftool!279]: Nonedominic/dune-perftool/merge_requests/279