Xcode 3.2.2 and 3.2.3 not supported and may cause errors

[Ron_Green]

UPDATE 12/2/2010: The underlying linker issue is fixed by Apple in Xcode 3.2.5. Please upgrade to this version of Xcode.



UPDATE 8/30/2010: This issue has a workaround in the 11.1 Update 7 compiler, posted to Intel Registration center (https://registrationcenter.intel.com). ALL users with Xcode 3.2.2 and above should upgrade to 11.1 Update 7, 11.1.089 or greater.






UPDATE 5/7/2010: Xcode 3.2.2 and Xcode 3.2.3 and ifort are not compatible and can cause incorrect runtime results or segmentation faults. A possible workaround is to add -use-asm option to all compile and ifort link commands (see below). We are continuing to work with Apple to resolve this issue.

READ THE PROBLEM WRITEUP HERE: http://software.intel.com/en-us/articles/intel-fortran-for-mac-os-x-incompatible-with-xcode-322/

The current Intel Compilers 11.1 officially support Mac OS* X 10.6.2 and Xcode* 3.2.1.

Unofficial testing indicates that Mac OS* X 10.6.3 and Xcode* 3.2.1 appear to work together with the compiler, however this configuration is not OFFICIALLY supported at this time.

However, Mac OS* X 10.6.3 and Xcode* 3.2.2 combination with the Intel Compilers v11.1 have at least 1 known critical issue under investigation. At this time we do not recommend upgrading Xcode to 3.2.2 (or later). This version of Xcode includes a new build of gcc/g++ and it's libraries that appear to affect the Fortran runtime library. We will post more information as the investigation continues.

If you are seeing unusual behavior for your previously working applications after the Xcode 3.2.2 please add a reply to this thread. Particularly if you see any Intel C or C++ issues. So far we only have reports from Fortran users.

Thanks

Ron W. Green, 28 April 2010

[Ron_Green]

The linker version is also shown in the Knowledge Base article on this issue here: http://software.intel.com/en-us/articles/intel-fortran-for-mac-os-x-incompatible-with-xcode-322/

[Dave_Allured]

Ken,

.

Thank you very much, the direct file address got the Xcode version number for me. I was not able to get the version number with either of the GUI methods because I have only command line access to the processor of interest.

[plain]mac78:~ 7> cat /Developer/Applications/Xcode.app/Contents/version.plist




	BuildVersion
	1
	CFBundleShortVersionString
	3.2.2
	CFBundleVersion
	1650
	ProjectName
	DevToolsIDE
	SourceVersion
	16500000


[/plain]

I confirmed that I had Xcode version 3.2.2 on this processor, thus my original symptom is indeed just the Xcode 3.2.2 problem.

.

Thanks to you and Ron for your help.

.

--Dave

[pbro1]

Ron,

the fortran main program calls the C subroutine. The constant "1" is defined in the C preprocessor and stored in a variable

[cpp]#define CONST 1
int var;
var = CONST;[/cpp]

(might actually become a real variable in a later version) and later:
ptr = (double *)malloc(var * sizeof(double));
causes the malloc problem, unless I insert a printf(""); before it.

The malloc problem appears, before the execution returns to the fortran part of the code. No fortran code is called from C. However, the initial C subroutine calls several C functions spread over different source code files (and thus over different .o object files).

Peter

[barry_j_mcinnes]

We just setup a 10.6.3 test desktop, and run in compile/link problems with Intel fortran.

Is there an ETA on when Intel will release a 3.2.2 compatible version, so we can plan for 10.6 deployment ?

[Ron_Green]

A fix is targeted for the next 11.1 compiler update, tendatively scheduled for mid-to-late August. We tend to do updates roughly every 3 months.

ron

[jcf2q]

Hey Ronald, I too would like to know the next 11.1 update.. any news on one? should be around that time..

[Ron_Green]

A fix is in the 11.1 Update 7 compiler, 11.1.089, which is posted to Intel Registration Center, https://registrationcenter.intel.com.

This compiler was posted late last week and activated.

ron

[Todd_Peterson]

Thanks for the info, Ron. To be clear, is this 11.1.089 okay to use with Xcode 3.2.3 as well as Xcode 3.2.2? The System Requirements section of the 11.1.089 release notes PDF seems to point to Xcode 3.2.2 as the most recent version with which you're compatible.

Kind regards,

Todd

[Ron_Green]

When Apple releases an Xcode version we have to play catch up, so the documentation an our QA and Validation teams lag a little. To date, no issues have been found with Xcode 3.2.3. However "officially" we are only supporting 3.2.2.

I don't know of any issues with 3.2.3, I've been using it myself for a while.

ron

[Ron_Green]

That is correct - there is a bug currently with C/C++ switch statements. There is a fix in the works for the next update release. Use -use-asm to work around the problem until it is fixed.

ron