Syntax error highlighting and "jump to" capabilities not functional under Xcode with Intel Fortran


Reference Number :  DPD200112358


Version : All 11.0 packages prior to 11.0.064


Operating System : Mac OS X* / IA-32, Intel® 64


Problem Description 

Format changes made to the Intel Fortran compiler diagnostic messages in the Intel Fortran Compiler Professional 11.0 release affect the parsing of the diagnostics as required to enable syntax error highlighting functionality under the Xcode IDE, and the "jump to" source location capability via a double-click on errors and warnings gathered for source files listed under the Errors and Warnings group under Groups & Files.

When using the Intel Fortran 11.0 compiler under Xcode, the syntax error highlights will not appear within the Fortran source code under the Xcode IDE as shown in Figure 1 below, and there is no "jump to" capability enabled when double-clicking errors or warnings listed in the Message pane corresponding to source files listed under the Errors and Warnings group under Groups & Files.

Xcode_error_highlights_11.0.bmp

Figure 1:
Xcode IDE with syntax error highlights disabled



When using the Intel Fortran 10.1 compiler, the syntax error highlights will appear within the Fortran source code under the Xcode IDE as shown in Figure 2 below, and the "jump to" capability is enabled when double-clicking errors or warnings listed in the Message pane corresponding to source files listed under the Errors and Warnings group under Groups & Files.

Xcode_error_highlights_10.1.bmp

Figure 2:
Xcode IDE with syntax error highlights enabled



Resolution Status 


Both issues discussed above are resolved in the Intel Fortran Compiler Professional Edition 11.0 update, package id: m_cprof_p_11.0.064.

In lieu of installing the specific 11.0.064 update, the functionality can onlybe re-enabled by using the Intel Fortran 10.1 compiler under Xcode as discussed below.

To use the Intel Fortran 10.1 compiler under Xcode, first download the latest Intel Fortran 10.1 compiler m_fc_p_10.1.024.dmg update package from the Intel Registration Center (https://registrationcenter.intel.com) and install the update. Next, start Xcode and open your Fortran Xcode project. Under Targets, right-click on the target name and select Get Info. Next, click on the Rules tab and then change the rule for Fortran source files to use the Intel Fortran Compiler 10.1 (Preview). The Xcode project can now be rebuilt.

The Intel Fortran 10.1 compiler restores the error highlights within the Fortran source code and the convenience of "jump to" the corresponding source location via double-clicking on warnings and errors listed in the Messages pane for source files listed under the Errors and Warnings group under Groups & Files. Once the Xcode project is compiling and running using the Intel Fortran 10.1 compiler, you may switch back to the Intel Fortran 11.0 compiler following the steps above for setting the rule for Fortran source files.



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

 

 

 

 

 

 

For more complete information about compiler optimizations, see our Optimization Notice.