Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29280 Discussions

ifort v11.1.059 (and higher) hangs on program that compiles with v11.1.056 and v10.1.015

kddevin
Beginner
1,095 Views
The attached program compiles with ifort v10.1.015. A similar program (from which this one is derived) compiled with ifort v11.1.056. But with v11.1.059, the compilation hangs -- no error message, just a lot of CPU being used and no output. The problem was also confirmed for v11.1.069 and 11.1.072.

Here is the output with v10.1.015 -- all good. Compilation takes about 2 seconds.
$ ifort -logo
Intel Fortran Compiler for applications running on Intel 64, Version 10.1 Build 20080312 Package ID: l_fc_p_10.1.015
Copyright (C) 1985-2008 Intel Corporation. All rights reserved.

$ ifort -c fwrap2.f90
fwrap2.f90(2001): (col. 21) remark: LOOP WAS VECTORIZED.
fwrap2.f90(2001): (col. 21) remark: LOOP WAS VECTORIZED.
fwrap2.f90(2001): (col. 21) remark: LOOP WAS VECTORIZED.
fwrap2.f90(2001): (col. 21) remark: LOOP WAS VECTORIZED.
fwrap2.f90(2001): (col. 21) remark: LOOP WAS VECTORIZED.
fwrap2.f90(2001): (col. 21) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1915): (col. 16) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1915): (col. 16) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1915): (col. 16) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1915): (col. 16) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1915): (col. 16) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1915): (col. 16) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1915): (col. 16) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1915): (col. 16) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1825): (col. 29) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1825): (col. 29) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1825): (col. 29) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1797): (col. 21) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1797): (col. 21) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1797): (col. 21) remark: LOOP WAS VECTORIZED.
fwrap2.f90(1797): (col. 21) remark: LOOP WAS VECTORIZED.

With v11.1.059, however, the compilation never completes and gives no output:

$ ifort -logo
Intel Fortran Intel 64 Compiler Professional for applications running on Intel 64, Version 11.1 Build 20091012 Package ID: l_cprof_p_11.1.059
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.

$ ifort -c fwrap2.f90

and nothing more.

I assume this is a compiler bug. Where should I report it? Is there a workaround?

Thanks from a newbie.




0 Kudos
5 Replies
Kevin_D_Intel
Employee
1,095 Views

Reporting it here is all that's needed and thank you for doing so. It appears the hang occurs in the front-end so I don't have an immediate work-around to offer. I willdig further and also reportit to Development (provide an internal tracking id below) and update this post as I learn more.

(Internal tracking id: DPD200157069)

(Resolution Update on 08/31/2010): This defect is fixed in the Intel Fortran Compiler Professional Edition 11.1 Update 7 (11.1.073 - Linux).

0 Kudos
Kevin_D_Intel
Employee
1,095 Views
I confirmed this defect is fixed in our internal 11.1 development compiler. I expect the fix to be in the next 11.1 Update 7 tentatively scheduled for later this month.
0 Kudos
kddevin
Beginner
1,095 Views
Thank you, Kevin. Is there a way I can try the development compiler on our larger library code? The example I posted was extracted from the library code.
0 Kudos
Kevin_D_Intel
Employee
1,095 Views
Unfortunately, no. The compilers are not in packaged form and are somewhat untested. If convenient, I would happily test the larger code if you want to provide that. You can take the thread private and post the code then delete once I have in-hand.
0 Kudos
Kevin_D_Intel
Employee
1,095 Views
The 11.1 Update 7 (11.1.073 - Linux) containing this fix is now available from the Intel Registration Center: https://registrationcenter.intel.com
0 Kudos
Reply