Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
1 result
You can move around the graph by using the arrow keys.
Created with Raphaël 2.2.018Feb15141312111087654131Jan302928242322211816111098721Dec18171413121110754328Nov26232221151413931Oct30262524232219181615121110854228Sep2721201917141312629Aug282724232221201615223Jul20191064319Jun151488May426Apr25242319181716131110929Mar28272623222120191615141398762128Feb[Bugfix] Fix typo[Bugfix] No opcounters in function arguments...use the same approach for driverReally turn off opcounting in autotuning benchmarksAdd infrastructure for sumfact kernel transformationsBuild file system synchronization into the autotuner.Correctly wati for output file with google benchamrkadd instrumentation level 4[cmake][bugfix] Correctly import google benchmark target[!315] Fix opcounter bug in google-benchmark autotuningFix opcounter bug in google-benchmark autotuningrestore old code path for matrices > 3x3add instrumentation level 3[!313] Feature/donkey autotune setup[Bugfix] Autotuning google benchmarks with fastdgadd driver instrumentationgenerate likwid performance measurementsFix return code handling in compilation wrapperpush return statement to end of blockrefactoring timings.pyChange file permissionsAdd a benchmark compilation wrapper[!311] Enabling vectorization for arbitrary number of blocksMerge branch 'feature/sumfact-loop-reordering' of ssh://gitlab.dune-project.org:22022/extensions/dune-codegen into feature/sumfact-loop-reordering[!312] Feature/autotuning google benchmarkFix pep 8Make a test that only runs if benchmark was found[!310] Change scaling of autotune results[cmake] find and use google benchmark through cmake[skip ci] bugfixadd testsrefactoringadd option for tail ordering[skip ci] TODO Do proper cmake integration[skip ci] Add test[skip ci] Make it possible to use google-benchmark for autotuningAdd include for intrinsicspep8Make sure autotune scores are floatsuse loopy to add dependencies

Datenschutz und Impressum