You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mat, DW, and I have been experimenting with compiler settings for libsharp. We seem to have found a factor of 2 runtime improvement using icc/ifort rather than gcc/gfort on nersc. In order to take advantage of this, it is necessary to use the same compilers for enlib/sharp and libsharp. Mat has found that this can work if one replaces
with LDSHARED="icc -shared" CC=icc $(PYTHON) setup.py build_ext --inplace
Could this change get made in the repo version? Could it check if the user is using the intel compiler (based on the contents of $ENLIB_COMP) and insert this if so?
The text was updated successfully, but these errors were encountered:
This issue is solved in the new analysis library: https://github.com/simonsobs/sotools and I will recommend closing it when our transition is complete.
Mat, DW, and I have been experimenting with compiler settings for libsharp. We seem to have found a factor of 2 runtime improvement using icc/ifort rather than gcc/gfort on nersc. In order to take advantage of this, it is necessary to use the same compilers for enlib/sharp and libsharp. Mat has found that this can work if one replaces
enlib/sharp/Makefile
Line 4 in 76c1a7b
LDSHARED="icc -shared" CC=icc $(PYTHON) setup.py build_ext --inplace
Could this change get made in the repo version? Could it check if the user is using the intel compiler (based on the contents of $ENLIB_COMP) and insert this if so?
The text was updated successfully, but these errors were encountered: