Segfault while compiling

[dschanen]

I get this message for a couple files on a project I'm trying to build here with the 9.1.032 compiler:

fortcom: Severe: **Internal compiler error: segmentation violation signal raised** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.
compilation aborted for (filename).F (code 3)

All I need to do is ifort -c (filename).F for both files.

This is on a Redhat Enterprise 3 machine, so it uses glibc-2.3.2 and a 2.4.21 kernel, if that makes any difference. I haven't tried it anywhere else. The files in question are modules with some preprocessing and some private and public components. They're also both fixed format and > 1000 lines.

[Steven_L_Intel1]

This is always a compiler bug. Please submit an issue to Intel Premier Support and attach everything necessary to reproduce the problem, including source files and command line used.

[dschanen]

I've been getting a error the past couple of days accessing premier support. Specifically: http://or1grebe.cps.intel.com/scripts-util/404.asp?Redirect=Y

Thanks,
David

[Steven_L_Intel1]

Some others have had this too. Please write to quad.support-at-intel.com (where -at- is @) for assistance with the Premier Support login problem.

[mrsmithmargaret]

Mr. Lionel, is there a general fix without sharing the files. We too are getting this error,Internal compiler error: segmentation violation signal raised,doing classified work and no files can be shared. The file which the Linux computer is not liking is 15,000 KB. Do you have any suggestions? Margaret

[Steven_L_Intel1]

Margaret,

There are many possible causes of this error. A fix for one user's problem may not fix your problem.

First, please make sure you are using the latest version of the compiler (11.1.064 is current) and that your shell datasize limit is high. Are you building a 32-bit or 64-bit application? Can you show me the command line options you are using?

You can also experiment with removing optimization-related switches or lowering the optimization level to see if that helps. Lastly, if your large file is composed of multiple routines, try splitting it into two or more files.