This repository was archived by the owner on Jan 25, 2023. It is now read-only.
Description Reorganize code base and initial version of numba-dppy extension
Move the numba.dppl package to its own repository (i.e. numba-dppy)
All core Numba changes to be outlined as patches needed to build Numba with numba-dppy
All patches need to be analyzed if they can be refactored or converted into plugins
PRs for cleaning unintended changes (make branch pydppl as close as possible to release0.51 branch):
PRs with patches (after refactoring it could be proposed to upstream , it is for starting discussion about this changes):
All upstream patches has label https://github.com/numba/numba/labels/dpPy .
PRs which should me moved to numba-dppy package:
Process current PRs to numba:
Patched version: #124
How to see our changes: git diff release0.51..pydppl
Recommended way of development now:
Create conda environment
Clone https://github.com/IntelPython/dpctl from branch master . Call: python setup.py develop.
Clone https://github.com/IntelPython/numba from branch patched . Call: python setup.py develop.
Clone https://github.com/IntelPython/numba-dppy from branch main . Call: python setup.py develop.
Install required conda packages if python setup.py develop shows that some packages are not installed.
Branches status
patched - contains release0.51 branch, minimal set of patches.
pydppl - contains all history, code similar to patched, numba-dppy subtree.
clean - contains all history, all patches removed, numba-dppy subtree removed - code the same as release0.51
patched-history - contains clean, minimal set of patches.
You should target your PRs to patched branch, because it is simpler than pydppl but contains the same code.
Reactions are currently unavailable
Reorganize code base and initial version of numba-dppy extension
numba.dpplpackage to its own repository (i.e.numba-dppy)PRs for cleaning unintended changes (make branch
pydpplas close as possible torelease0.51branch):cpu_dispatchermodifies global state #89 @PokhodenkoSAcpu_dispatchermodifies global state #89PRs with patches (after refactoring it could be proposed to upstream, it is for starting discussion about this changes):
numba-dppywith device_contextnumba/numba#6899ufunc_dbvia context numba/numba#6467replace_functions_mapvia PreParforPass instance numba/numba#6468All upstream patches has label https://github.com/numba/numba/labels/dpPy.
PRs which should me moved to
numba-dppypackage:numba-dppy#109 @PokhodenkoSA - reviewed with @reazulhoquenumba-dppy#110 @PokhodenkoSA - reviewed with @reazulhoquenumba-dppy#107 @PokhodenkoSA - reviewed with @reazulhoquenumba-dppynumba/dppl- delete it after all other PRsnumba-dppyProcess current PRs to numba:
numba-dppyPatched version: #124
How to see our changes:
git diff release0.51..pydpplRecommended way of development now:
python setup.py develop.python setup.py develop.python setup.py develop.python setup.py developshows that some packages are not installed.Branches status
patched- containsrelease0.51branch, minimal set of patches.pydppl- contains all history, code similar topatched,numba-dppysubtree.clean- contains all history, all patches removed,numba-dppysubtree removed - code the same asrelease0.51patched-history- containsclean, minimal set of patches.You should target your PRs to
patchedbranch, because it is simpler thanpydpplbut contains the same code.