The x and y passed to dgemm in that code are pointers to the same memory,
thus breaking Fortran's no-aliasing rule. Is it possible the MKL depends
on the
caller following that rule?
You might try dsyrk() instead of dgemm.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Mon, Jan 8, 2018 at 6:57
Hi Guillaume,
In principle, mycrossprod function does not need to PROTECT "ans",
because it does not call any allocating function after allocating "ans"
("dgemm" in particular should not allocate from the R heap). So it is
surprising that PROTECTion makes a difference in your case. I agree
the
Hi, I’d like to ask about bug 17159:
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17159
I can confirm that I see exactly this bug when using dir.create on paths of UNC
form (\\server\share\xxx), with the recursive flag set. I’m seeing this when
attempting to use install.packages with suc
