2020-04-27 06:50:23 +08:00
|
|
|
# npcomp - An aspirational MLIR based numpy compiler
|
|
|
|
|
|
|
|
|
|
## Scratch-pad of build configurations that have worked
|
|
|
|
|
|
2020-04-27 07:32:10 +08:00
|
|
|
## Quick start
|
2020-04-27 06:50:23 +08:00
|
|
|
|
2020-04-27 07:32:10 +08:00
|
|
|
```
|
|
|
|
|
export LLVM_SRC_DIR=/path/to/llvm-project
|
|
|
|
|
./tools/install_mlir.sh
|
|
|
|
|
./tools/cmake_configure.sh
|
|
|
|
|
|
|
|
|
|
cd build
|
|
|
|
|
ninja
|
|
|
|
|
./python/run_tests.py
|
2020-04-27 06:50:23 +08:00
|
|
|
```
|
|
|
|
|
|
|
|
|
|
### Installing pybind11
|
|
|
|
|
|
|
|
|
|
The native extension relies on pybind11. In a perfect world, this could just
|
|
|
|
|
be installed with your system package manager. However, at least on
|
|
|
|
|
Ubuntu Disco, the system package installed with broken cmake files.
|
|
|
|
|
|
|
|
|
|
I built/installed from pybind11 head without issue and put it in /usr/local.
|
|
|
|
|
There are better ways to do this.
|
|
|
|
|
|
|
|
|
|
### Building the python native library
|
|
|
|
|
|
|
|
|
|
```shell
|
|
|
|
|
# From the build directory
|
|
|
|
|
ninja NPCOMPNativePyExt
|
|
|
|
|
# Outputs to tools/npcomp/python/npcomp/native...so
|
|
|
|
|
export PYTHONPATH=$(pwd)/tools/npcomp/python
|
|
|
|
|
python3 -m npcomp.smoketest
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Notes:
|
|
|
|
|
|
|
|
|
|
* Python sources are symlinked to the output directory at configure time.
|
|
|
|
|
Adding sources will require a reconfigure. Editing should not.
|
|
|
|
|
* It is a very common issue to have both python 2.7 (aka. "python") and python
|
|
|
|
|
3.x (aka. "python3") on a system at a time (and we can only hope that one
|
|
|
|
|
day this ends). Since the native library at development time binds to a
|
|
|
|
|
specific version, if you try to run with a different python, you will get
|
|
|
|
|
an error about the "native" module not being found.
|
