Re: Windows array allocation problem

Richard Maine wrote:

g77 has
(or at least had - I don't know whether it changed) a limit based on the
array size in bits fitting in a 32-bit integer. Yes, that is bits, not
bytes. That's just how the internals of the compiler worked; it isn't a
limit you'd guess from looking at anything in Fortran language in
general.
In the context of 64-bit OS, had is the word. g77 maintenance ended
short of much support of 64-bit. Any more recent compiler would be a
better choice. Since you are diving into past history, I'll go further
into trivia and mention that g77 array size limit was changed at the end
so that 2GB arrays could be supported on 32-bit and x86-64, and 4GB
arrays on IA-64 (not that you would ever want to use that compiler).
.

Relevant Pages

  • Re: Idea for ECMA/C# Standard - compile time hash for performance
    ... I agree with you the chance of a compiler change is slim, ... and then delegating to the standard hash for fields accessed less frequently. ... or the array lookup which would require the ... > 64-bit architecture) for each enum value that doesn't map to anything. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Q: Checking the size of a non-allocated array?
    ... an actual argument is already invalid ... First note that you don't have an unallocated array in the subroutine. ... it is comparable to disassociated or undefined pointers. ... Obviously the compiler has ...
    (comp.lang.fortran)
  • Re: Windows array allocation problem
    ... array reference has to have a 64-bit index or array subscript triplet? ... to fit in one. ... That assumes, of course, that your compiler ... limits on just about anything. ...
    (comp.lang.fortran)
  • Bounds checked arrays
    ... As everybody knows, the C language lacks ... When the state of this toggle is ON, the compiler ... Important is to know that the array updates ... We have just to allow him/her to specify what to do ...
    (comp.lang.c)
  • Re: Error handling library
    ... which lets the compiler catch out-of-range usage. ... and assuming that a higher int means "more dangerous error" ... with a comment warning that one is used as an index into the array ... languages while running (an array of languages, ...
    (comp.lang.c)