- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI
I got very strange behavior of MKL. With MKL linked in my program, in the debug module I monitored the result for
one line of pure fortran code becomes NaN. Linked to source code of blas instead of MKL, the result of that line of fortran code is normal.
I am wondering how MKL infulence the behavior of the program even on the intrinsic operation like mulitplicaiton.
Thanks.
I got very strange behavior of MKL. With MKL linked in my program, in the debug module I monitored the result for
one line of pure fortran code becomes NaN. Linked to source code of blas instead of MKL, the result of that line of fortran code is normal.
I am wondering how MKL infulence the behavior of the program even on the intrinsic operation like mulitplicaiton.
Thanks.
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - optistruct
HI
I got very strange behavior of MKL. With MKL linked in my program, in the debug module I monitored the result for
one line of pure fortran code becomes NaN. Linked to source code of blas instead of MKL, the result of that line of fortran code is normal.
I am wondering how MKL infulence the behavior of the program even on the intrinsic operation like mulitplicaiton.
Thanks.
I got very strange behavior of MKL. With MKL linked in my program, in the debug module I monitored the result for
one line of pure fortran code becomes NaN. Linked to source code of blas instead of MKL, the result of that line of fortran code is normal.
I am wondering how MKL infulence the behavior of the program even on the intrinsic operation like mulitplicaiton.
Thanks.
This behavior only happens on 32 bit RH Linux machine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One possibility is that passing bad data to an MKL function could cause it to exceed array bounds and write garbage where you didn't expect it. Setting debug mode in your program doesn't set it in MKL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - tim18
One possibility is that passing bad data to an MKL function could cause it to exceed array bounds and write garbage where you didn't expect it. Setting debug mode in your program doesn't set it in MKL.
Optistruct, probably tim is right, but for investigation the problem - can you get us the test case?
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