-
Notifications
You must be signed in to change notification settings - Fork 6.8k
can compile with MKLDNN + MKLML but no MKL #15483
Comments
Hey, this is the MXNet Label Bot. |
@MaeThird thanks for trying MXNet with MKLDNN backend. Please paste the error message when you build without MKL. |
Hi @pengzhao-intel
It turns out MKLML cannot replace the MKL as the blas using.
with GCC-9.1 . It's handy to fix it. |
MKLDNN + MKLML + USE_BLAS_MKL=1 (Actually there was no MKL,I just replaced it with MKLML) with the error output: This is not the right usage because MKLML is just a subset of MKL and only works for MKL-DNN library. You can get MKL by yum or apt to avoid web register. As you see the "vsErf" is not included in MKLML but it's a part of MKL. cc @TaoLv |
@pengzhao-intel Thanks for your help. |
Thanks for pinging, @pengzhao-intel . Regarding the first error, yes, the vsErf function is not part of MKLML. So you need full MKL to take advantage of this function. |
Because MKL is really large and needs register in Intel' web. It's tedious in the production environment.
I tried to compile the mxnet with MKLDNN and MKLML without MKL but failed in the linking processing. It looks like the 'mshadow' module needs the MKL
I think if the entire MKL is convenient there will be no MKLML anymore. if the proj is not designed for production it's just a toy for ever.
The text was updated successfully, but these errors were encountered: