Browse Source

Merge pull request #5009 from martin-frbg/pybenchdoc

DOCS, pybench : Add build notes for Windows and flang from gh Discussion 5008
tags/v0.3.29
Martin Kroeker GitHub 1 year ago
parent
commit
72f7b7011c
No known key found for this signature in database GPG Key ID: B5690EEEBB952194
1 changed files with 11 additions and 1 deletions
  1. +11
    -1
      benchmark/pybench/README.md

+ 11
- 1
benchmark/pybench/README.md View File

@@ -43,7 +43,17 @@ have all what it takes to build OpenBLAS from source, plus `python` and
$ python -mpip install numpy meson ninja pytest pytest-benchmark
```

The benchmark syntax is consistent with that of `pytest-benchmark` framework. The incantation to run the suite locally is `$ pytest benchmark/pybench/benchmarks/test_blas.py`.
The Meson build system looks for the installed OpenBLAS using pkgconfig, so the openblas.pc created during the OpenBLAS build needs
to be somewhere on the search path of pkgconfig or in a folder pointed to by the environment variable PKG_CONFIG_PATH.

If you want to build the benchmark suite using flang (or flang-new) instead of gfortran for the Fortran parts, you currently need
to edit the meson.build file and change the line `'fortran_std=legacy'` to `'fortran_std=none'` to work around an incompatibility
between Meson and flang.

If you are building and running the benchmark under MS Windows, it may be necessary to copy the generated openblas_wrap module from
your build folder to the `benchmarks` folder.

The benchmark syntax is consistent with that of `pytest-benchmark` framework. The incantation to run the suite locally is `$ pytest benchmark/pybench/benchmarks/bench_blas.py`.

An ASV compatible benchmark suite is planned but currently not implemented.


Loading…
Cancel
Save