topic Re: Illegal Instruction when calling dgemv on Mac Pro in Intel® oneAPI Math Kernel Library

Illegal Instruction when calling dgemv on Mac Pro

jpritchardcfa_harvar — Fri, 03 Apr 2009 14:05:20 GMT

I'm trying to compile and run code with ifort linking MKL on a Mac Pro running Leopard. The code compiles fine, but when run it terminates with an "Illegal instruction" message when it calls dgemv. The same code compiles and runs without problem on my Macbook Pro running Tiger. I'm stumped.

Has anyone run into the same problem or know how to resolve it?

Cheers,

Jonathan

Re: Illegal Instruction when calling dgemv on Mac Pro

Gennady_F_Intel — Sun, 05 Apr 2009 18:33:02 GMT

Jonathan,
what mkl version you are using? And what is your linking line?
--Gennady?

Re: Illegal Instruction when calling dgemv on Mac Pro

jpritchardcfa_harvar — Thu, 09 Apr 2009 13:09:58 GMT

Quoting - Gennady Fedorov (Intel)

Jonathan,
what mkl version you are using? And what is your linking line?
--Gennady?

I'm using MKL version 10.0.5 with ifort 10.1 (I tried with ifort 11.0 with the same results)

The relevant lines in my Makefile for the linking are below:

MKLLIB=/Library/Frameworks/Intel_MKL.framework/Versions/10.0.5.025/lib/em64t

MKLINC=/Library/Frameworks/Intel_MKL.framework/Versions/10.0.5.025/include

LAPACK = -L$(MKLLIB) -lmkl_lapack -lmkl_intel_lp64 -lmkl_core -lguide -lpthread

F90 = ifort

FFLAGS = -O2

INCS = -I. -I$(CFITSIO)/include -I$(MKLINC)

LIBS = -L. -L$(CFITSIO)/lib -lcfitsio $(LAPACK)

test: $(OBJS) test.o

$(F90) $(FFLAGS) $(INCS) -o $@ test.o $(OBJS) $(LIBS)

Thanks!

Jonathan

Re: Illegal Instruction when calling dgemv on Mac Pro

TimP — Thu, 09 Apr 2009 13:35:13 GMT

Quoting - jpritchardcfa.harvard.edu

LAPACK = -L$(MKLLIB) -lmkl_lapack -lmkl_intel_lp64 -lmkl_core -lguide -lpthread

F90 = ifort

FFLAGS = -O2

INCS = -I. -I$(CFITSIO)/include -I$(MKLINC)

LIBS = -L. -L$(CFITSIO)/lib -lcfitsio $(LAPACK)

I'd worry about this combination of libraries. Since you gave lp64, you must be using 64-bit OS and 64-bit integer data in your MKL calls, and there ought to be a recommendation for that combination in the docs.
I would be more comfortable with
LAPACK= -lmkl_intel_lp64 -lmkl_core -lmkl_thread
FFLAGS = -O2 -openmp
as you said you were using an ifort which should have its own MKL installation.
The most worrisome part is your attempt to link both 32-bit and 64-bit integer data support. You can't have it both ways.