Closed mcjinye closed 5 years ago
As I'm investigating why Intel C++ compiler (severely) breaks the libint compiler I recommend you only use icpc
to compile generated code only e.g.
...../configure CXX=g++ CXXFLAGS='-std=c++11 -mtune=native -O2' CXXGEN=icpc CXXGENFLAGS=' -std=c++11 -xHOST -O3'
(there is no dramatic benefit to using icpc
to compile the libint compiler anyway).
Another workaround is to use non-Intel compiler to generate an export library (configure with g++
or clang++
and do make export
), then use the generated tarball to configure and compile with icpc
. An extra step, but unless you are developing libint there is no benefit to doing in-compiler compilation of the libint library.
bump: is this still an issue?
I think it's fixed already. Thanks!
On Mon, Jun 3, 2019, 08:51 Eduard Valeyev notifications@github.com wrote:
bump: is this still an issue?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/evaleev/libint/issues/106?email_source=notifications&email_token=AKDFKJHLQDVVHXIYKJBXGN3PYUHWFA5CNFSM4FPMZDZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWZJNNY#issuecomment-498243255, or mute the thread https://github.com/notifications/unsubscribe-auth/AKDFKJBLX6IRNTRUN2OGKBTPYUHWFANCNFSM4FPMZDZA .