- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A call of dgesvd with a random matrix results in a segmentation fault. I work with MKL 8.0.2 on a Pention IV with Linux. A call of dgesvd with the same matrix using LAPACK leads to no error.
My program reads:
program ftest
integer M
integer N
integer Q
integer LWORK
parameter (M=300)
parameter (N=400)
parameter (Q=300)
parameter (LWORK=100000)
double precision A(M,N)
double precision U(M,M)
double precision VT(N,N)
double precision S(Q)
double precision WORK(LWORK)
integer INFO
do i=1,M
do j=1,N
A(i,j) = rand(0)
end do
end do
call dgesvd('A','A',M,N,A,M,S,U,M,VT,N,WORK,LWORK,INFO)
stop
end
I compile it with the command:
ifort ftest.f -lmkl_lapack -lmkl -lguide -o ftest
Is this a MKL-bug or a wrong usage of the function dgesvd?
Thanks for your interest!
My program reads:
program ftest
integer M
integer N
integer Q
integer LWORK
parameter (M=300)
parameter (N=400)
parameter (Q=300)
parameter (LWORK=100000)
double precision A(M,N)
double precision U(M,M)
double precision VT(N,N)
double precision S(Q)
double precision WORK(LWORK)
integer INFO
do i=1,M
do j=1,N
A(i,j) = rand(0)
end do
end do
call dgesvd('A','A',M,N,A,M,S,U,M,VT,N,WORK,LWORK,INFO)
stop
end
I compile it with the command:
ifort ftest.f -lmkl_lapack -lmkl -lguide -o ftest
Is this a MKL-bug or a wrong usage of the function dgesvd?
Thanks for your interest!
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Works fine with MKL 7.2 (Cluster)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Segmentation fault also with MKL 8.0 on an Intel Xeon 64bit. According to the debugger, the error is in function mkl_blas_dgemm_copybt() in libmkl_p4n.so.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
http://softwareforums.intel.com/en-us/forums//topic/51912
I have a similar problem 8.0.1 with matrix sized 350x320. Couldn't find any solution.
Laszlo

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