Re: gfortran, g95, and dual-core
Richard Maine wrote:
If you had listened to the sound of the disk drive going wild while
compiling, as I often have done, you'd know that the compiler is often
very disk intensive. Mostly, I think that is because an optimzing
compiler can use huge amounts of memory, which can cause virtual memory
swapping.
Perhaps the reason I haven't noticed is that I always have all available
debugging features enabled, which probably switches off most of the
optimization. In fact, I don't recall using any compiler prior to g77
that did any optimization under those circumstances.
.
Relevant Pages
- Re: Windows array allocation problem
... I've just written a program which does nothing except call GlobalMemoryStatus to get the available virtual memory, then allocates an array to that size and in decreasing steps until STAT returns zero. ... The maximum allocation is consistently 146 MB less than the reported available virtual memory. ... So the phenomenon isn't due only to how Windows handles virtual memory but how the compiler handles it. ... The test shows that even for the simplest program, the Intel compiler doesn't allow allocating as much of the application virtual memory as the Compaq compiler does, at least not to one large array. ...
(comp.lang.fortran) - Re: Insufficient virtual memory
... the program stops with the error message "insufficient ... It might be that virtual memory really is too small, ... compiler writers were good at minimizing the ...
(comp.lang.fortran) - Re: Simple code doesnt work on two systems
... tried to run it on my friend's computer (he doesn't have the compiler). ... but is terminated by Windows. ... Now I know for a fact that my roommate has his Virtual Memory size set to zero. ... "It is easy in the world to live after the world's opinion; it easy in solitude to live after our own; but the great man is he who in the midst of the crowd keeps with perfect sweetness the independence of solitude." ...
(microsoft.public.dotnet.languages.vc) - Re: Ternary operator and memory access
... crafted compiler conning. ... There is no language construct that will guarantee that no virtual memory access will be generated to an object; a compiler would in principle be free to do this "whenever it felt like it", provided it could guarantee this would not cause the program to abort or invoke other nonconforming behavior. ...
(comp.lang.c) - Re: Windows array allocation problem
... allocate an array to a size which is about 385 MB less than the amount of available virtual memory. ... I'm using the Intel Visual Fortran v. 9.1 compiler, with the compiler and program running under Windows XP. ...
(comp.lang.fortran) |
|
