topic Re: Snow Leopard Support Status in Intel® Fortran Compiler

Snow Leopard Support Status

Ron_Green — Mon, 31 Aug 2009 18:14:06 GMT

Mac OS X 10.6, also known as Snow Leopard, is supported by the Intel Fortran Compiler Professional Edition for Mac OS X as of compiler version 11.1.067 (and newer 11.1 versions).

ISSUE with 11.1.067 MKL library (and C++ libs TBB and IPP): these libraries bundled with Intel Compiler Professional Edition v 11.1.067 are NOT compiled for Snow Leopard. An update compiler to be released in the future will address this issue. I will post a message when there is a compiler update containing MKL for Snow Leopard. Typical error you will see is 'section not found for address 0x'.

This version of the compiler is available for all users with active support licenses at https://registrationcenter.intel.com. This was posted to registrationcenter September 21st, 2009.

ron

Re: Snow Leopard Support Status

dradamschultz — Wed, 02 Sep 2009 22:29:36 GMT

Quoting - Ronald W. Green (Intel)

Mac OS X 10.6, also known as Snow Leopard, is not supported by the Intel Fortran Compiler Professional Edition for Mac OS X at this time (August/early September 2009).

Support for Snow Leopard will appear in the 11.1 Update 2 compiler which will come out around mid-September 2009.

ron

I've just placed an order (on 9/2/09) for Intel Fortran Compiler Professional Edition for Mac OS X V11.1 to run on a MacPro that as of today is running OS X 10.6 Snow Leopard. Browsing through your support forum, I see from the thread above that this product is not yet supported under OS 10.6, but that a mid-September patch is anticipated. Just confirming that there is a reasonably firm date when I can expect the patch to be released. I need to have a functioning Intel fortran compiler in the next week or so as I begin a new project.

Also, once support for Snow Leopard is official, I am wondering about support for OpenCL and Grand Central Dispatch. The potential to harness the floating point cycles of the GPUs through OpenCL is particularly appealing, and am hoping there are developments within Intel compilers to take advantage of this in the near future. Any information you have about this would be greatly appreciated. I should mention that by going through this process, I am transitioning away from Absoft and gfortran to Intel products, so have high hopes for this sort of level of system optimization by adopting Intel development tools.

Re: Snow Leopard Support Status

Ron_Green — Mon, 14 Sep 2009 21:06:46 GMT

Quoting - dradamschultz

9/14/2009 There was a slight delay on the compiler update 2 release, but it's not far off (assuming no more last minute problems). I would guess in 1 week and a few days,maybe 2weeks worse case. Again, we do not commit to release dates until we're sure we are finished with product validation and QA approval to release and we're not there as of today.

OpenCL: Intel does participate with the broader OpenCL project. However, at this time there are no plans to support OpenCL in our compilers. It is a technology we are watching closely and assisting where we can. I too hope this succeeds, and many customers prefer and open standard to something proprietary to a particular vendor.

And a final note: Like a lot of software vendors, we will lag new releases on Mac OS X, Linux and Windows by a few months or more. We cannot qualify our software until we have OFFICIAL releases of the OS. Yes, we test and work fixes using beta software, but our processes require us to hold off our testing product validation (PV) and QAfor official releases. Thus, after the official release, we have to line up the next update for compliance testing, get the PV and QA servers configured, wait for the next update and then validate. It's not instantaneous. Vendors have a habit of unleasing 'surprises' in the final releases so we do not validate against beta, hoping the release is identical. Too risky.

ron

Re: Snow Leopard Support Status

Steve_Elgar — Tue, 22 Sep 2009 23:57:30 GMT

Quoting - Ronald W. Green (Intel)

Mac OS X 10.6, also known as Snow Leopard, is supported by the Intel Fortran Compiler Professional Edition for Mac OS X as of compiler version 11.1.067 (and newer 11.1 versions).

This version of the compiler is available for all users with active support licenses at https://registrationcenter.intel.com. This was posted to registrationcenter September 21st, 2009.

ron

Re: Snow Leopard Support Status

Steve_Elgar — Wed, 23 Sep 2009 00:00:02 GMT

Quoting - Ronald W. Green (Intel)

I have installed Snow Leopard, updated it to 10.6.1, installed xcode and X11. I then installed fortran 11.1.067.

i try to compile and get this error:
Assertion failed: (truncated uleb128 expression), function getULEB128, file /usr/local/include/libunwind/AddressSpace.hpp, line 152.

I do not have a /usr/local/include, and it appears my former 10.5.8 system did not have /usr/local/include either, but the same ifort command (ifort file.f or ifort -O3 -o file file.f) worked fine.

Re: Snow Leopard Support Status

Steve_Elgar — Wed, 23 Sep 2009 00:30:22 GMT

Quoting - Ronald W. Green (Intel)

My ifort errors seem to be associated with libraries (eg, libfft.a) that I put in ,,,/lib.

I use the same procedue I have used for years:

1) cp libfft.a from an archive to .../067/lib/libfft.a
2) ranlib libfft.a

In the past thast was all I needed to do. Then coompile with:
ifort file.f -lfft

This seems to be failing for two libraries. One gives me the error:
/usr/local/include/libunwind/AddressSpace.hpp, line 152

The other library tells me:

I tired using the ia32 compiler (11.1.067) and it tells me: file is not of required architecture.

So, do you know the propoer steps to take a file full of fortran subroutines and turn them into a library
that can be loaded with "ifort ... -llibraryname?

ld: in /usr/bin/ifort-11.1-base/lib/libnag.a(c06faft.o), section not found for address 0xFFFFFFFFFFFFFD14

Re: Snow Leopard Support Status

irhooper — Fri, 09 Oct 2009 17:51:56 GMT

Quoting - Ronald W. Green (Intel)

From this thread it appears that there is now a version of MKL which will run on Snow Leopard. Is there any way to obtain this so that I can really evaluate the compiler?

Thanks for any help,

Ian

Re: Snow Leopard Support Status

Reinaldo_Garcia — Sun, 15 Nov 2009 16:58:06 GMT

Quoting - irhooper

I am using Snow Leopard and have downloaded the 30 day evaluation. The software I would like to test it on uses LAPACK routines and since the evaluation software appears to include MKL 11.1.067 I cannot run it as per the original post (or at least this appears to be the problem).

From this thread it appears that there is now a version of MKL which will run on Snow Leopard. Is there any way to obtain this so that I can really evaluate the compiler?

Thanks for any help,

Ian

Re: Snow Leopard Support Status

Reinaldo_Garcia — Sun, 15 Nov 2009 16:59:48 GMT

Quoting - Reinaldo Garcia

I installed Snow Leopard 10.6.2 and my previous compiler v11.0 did not work. I updated to 11.1.076 and all seems to be working fine now.

Re: Snow Leopard Support Status

DOS_SANTOS__LUIZ_RAF — Mon, 16 Nov 2009 01:01:29 GMT

Quoting - Reinaldo Garcia

I installed Snow Leopard 10.6.2 and my previous compiler v11.0 did not work. I updated to 11.1.076 and all seems to be working fine now.

R

Reinaldo,

Did you used the MKL Libraryv (Math). Please, that was the issue that we have been reporting. If that's working I'll install Snow Leopard. Otherwise I'll skip and wait.

Re: Snow Leopard Support Status

Kevin_D_Intel — Mon, 16 Nov 2009 10:17:45 GMT

The specific error Ron noted with 11.1.067 (Mac OS) involving the 'section not found for address 0x' impacting the performance libraries (TBB, IPP, MKL) is reportedly fixed in the latest 11.1 Update 3 (11.1.076 - Mac OS) release.

The Internal tracking id is:DPD200140030

Re: Snow Leopard Support Status

Raph — Wed, 27 Jan 2010 22:05:38 GMT

Hi-

I just upgraded from 10.5.8 to 10.6.2 and, as instructed, reinstalled ifort 11.1.080. I see a similar error to that reported when I try to compile as I have in the past, with-ipo -O3 -xT -mdynamic-no-pic -no-prec-div -autodouble

ld: in /var/folders/EH/EHnPHq7RHA4K3TDOT18kbI2wqow/-Tmp-/ipo_ifortABGmZw.o, section not found for address 0x100002EC0

where earlier in the compile ipo reports

ipo: remark #11005: generating object file /var/folders/EH/EHnPHq7RHA4K3TDOT18kbI2wqow/-Tmp-/ipo_ifortABGmZw.o

If I try to compile for debugging,-V -g -check all -check noarg_temp_created -fpe0 -traceback -autodouble , I instead get a different but similar error.

ld: in data.o, section not found for address 0x100002F50

From the discussion in this thread, I'd thought this was a solved problem (which kept be from upgrading to Snow Leopard until now). Any ideas what I'm doing wrong?

Raph

Snow Leopard Support Status

Wolfgang_Knorr — Fri, 29 Jan 2010 20:45:54 GMT

Hi,

has anyone come across this problem? I also upgraded from Mac OS 10.5.8 to Mac OS 10.6.2, and from ifort11.0/054 to 11.1/080. The initial problem with 11.0 was solved, and code compiles fine. But I get another strange problem: interrupt does not seem to work. Control-C does not stop the process (while it stops other processes, so it's not the terminal), and when the code encounters an error (it does at least on the 10.5.8 machine, but exits with error message), the program just hangs in there with 9% CPU time, and you have to kill it with kill -9. As said, with OS 10.5.8 this all works fine.

I compile with

ifort-assume byterecl

everything else default.

Thanks for anyone who could help.

Wolfgang

Snow Leopard Support Status

Kevin_D_Intel — Sun, 31 Jan 2010 13:59:53 GMT

Please excuse the delayed replies.Just overlooked the posts to this sticky post. I might recommend in the future starting a new thread and referring back to a sticky post.

Raph: There's no evidence from the snippets of options provided that you are using MKL, but if you are, can you confirm you installed the latest MKL from 11.1 update 4 (11.1.080) also?

In the optimized build. the error clearly involves an IPO generated object. In the debug case, do you have a corresponding source file, data.f90 (or similar)?

Any possibility of our obtaining a test case for either or both errors?

Wolfgang: Thereis a report of exception catch being ignored on Mac OS 10.6.2 with 11.1 compilers (here), but I don't know if it is related to your issue.

I can try reproducing with smaller a test case, but if you can provide a small reproducer that would be helpful.

It might a long shot, but you could try the suggested work around from the earlier thread of linking with (-Xlinker -no_compact_unwind or -Wl,-no_compact_unwind)