- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
6 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yes, this is strange, but it is true. There no problems on win32. We will check what's going on with this case and will back to you asap.
--Gennady
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- as a temporarily workaround: theproblemis not visible if the Intel C/C++ Compiler will be used instead of Microsoft C/C++.
--Gennady
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Gennday.
As a workaround, I added a dummy call to fmod right after those two Lapack functions. I'm really curious how this happened.
As a workaround, I added a dummy call to fmod right after those two Lapack functions. I'm really curious how this happened.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jaewon,
I'm debugging your testcase. Here's what I've found.
fmod relies on the specific status word contents, but for some reason MKL changes the status word. In the particular case fmodgoes to an exception route because it doesn't expect this specific status word.
To my experience, this issue happens with Microsoft cl only, but not with Intel compiler.
I'm going to narrow down the issue and fix it in the upcoming MKL update.
Thank you for the good testcase.
Michael.
I'm debugging your testcase. Here's what I've found.
fmod relies on the specific status word contents, but for some reason MKL changes the status word. In the particular case fmodgoes to an exception route because it doesn't expect this specific status word.
To my experience, this issue happens with Microsoft cl only, but not with Intel compiler.
I'm going to narrow down the issue and fix it in the upcoming MKL update.
Thank you for the good testcase.
Michael.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jaewon,
I have an update on this issue.
First, fmod issue on x64 is a known MS issueposted at http://support.microsoft.com/kb/972497, so use this functionwith cautionin x64, or use Intel compiler where there's no issue with fmod.
Second, changing SW is legitimate by callee, that is, by MKL, the callee doesn't have to restore SW on exit.
So we won't change MKL behaviour regarding to this issue.
Michael.
I have an update on this issue.
First, fmod issue on x64 is a known MS issueposted at http://support.microsoft.com/kb/972497, so use this functionwith cautionin x64, or use Intel compiler where there's no issue with fmod.
Second, changing SW is legitimate by callee, that is, by MKL, the callee doesn't have to restore SW on exit.
So we won't change MKL behaviour regarding to this issue.
Michael.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Michael,
I didn't know. Thank you so much for your time.
Best,
Jaewon
I didn't know. Thank you so much for your time.
Best,
Jaewon
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page