I'm having some difficulty compiling CASTEP, a F90 plane-wave
electronic structure code with ifort Build 20050912Z Package ID: l_fc_c_9.0.027. While compiling one of the major modules the
fortcom process grows in size until it uses 1GB of memory. What happens next depends on the optimization level:
-O0 and -O1 : the compile succeeds
-O2 and -O3 on a machine with 1GB memory
ilio_malloc: out of memory -- 23dc405c bytes requested
fortcom: Severe: **Internal compiler error: internal abort**
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.
and indeed there is no way a malloc of 600MB on top of 1GB allocated could succeed. On another machine with 1.5GB memory
the machine begins swapping and grinds to a near-halt, but eventually the compile succeeds.
What really surprises me is that even a -O0 compilation demands
1GB. Are there any hidden flags which tune the optimization
which could be used to test this further?
Keith Refson
