Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Ron_Cohen
Beginner
90 Views

BUG in P?GEMM remains

The bug in Scalapack  P?GEMM seems not to be fixed even in the 2017 beta3 library , although it has apparently been known since at least June . It seems to be present since mkl 11.3 . It works fine in mkl 11.2 . See here for the previous discussion.

0 Kudos
5 Replies
Gennady_F_Intel
Moderator
90 Views

Ron, I don't know what MKL 2017 beta3 is... Actually we had only MKL 2017 beta 1 :).  Nevertheless, checking the internal database, I see this issue is targeted to MKL 2017 ( released Sep 6th 2016). Could you please check your case with this version and let us know how it work?  wbr, Gennady

 

Ron_Cohen
Beginner
90 Views

Yes I tried that and it did not work. It was the same as 11.3 . On the superMUC machine here in Germany there is 2017 beta1 beta2 and beta3 . It doesn't work for any of those.

 

Ron_Cohen
Beginner
90 Views

here are the dates that I find:

Apr  6 00:57 studio2017_beta1

Jun  3 12:46 studio2017_beta2

Jul 14 12:28 studio2017_beta3

Sep  6 20:07 studio2017

It sounds like I should be using studio2017 although no module points to it  I will try it.

Thanks!

 

Ron_Cohen
Beginner
90 Views

OK, so I tried 2017 (with no beta) and it does work. It is slower than 11.2 for my test case, but it could be because my test case is too small. So it seems like it is fixed in 2017. Thank you!

 

Gennady_F_Intel
Moderator
90 Views

quote - "It is slower than 11.2 for my test case..."  . Ron, in the case if p?gemm  from 2017 version is slower vs 11.2 for reasonable problem sizes, please let us know. thanks, Gennady

Reply