This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Question
- To: Michael dot I dot Miga at Dartmouth dot EDU
- Subject: Re: Question
- From: "Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>
- Date: Wed, 31 May 2000 19:32:45 +0200
- CC: gcc-bugs at gcc dot gnu dot org
- References: <31961249@dasher.Dartmouth.EDU>
> Below is the program followed by the bug at compile time. This
> should not be a problem for my machine...the stack size is set to
> unlimited and I have 1 Gig of Ram. This array should only be about
> 600 Megs. I have done some tests and the program bails when the
> array gets above 264 megs +/- a little.
> Any clues..
This is a known problem: GCC internally represents the size of an
array as the number of bits, instead of the number of bytes; so that
range overflows unsigned 32bit. You either need to make the array
slightly smaller, or use a 64-bit-machine.
> or any suggestions on a different fortran compiler?
This is the GCC list :-)
> Does gcc have the same bug?
Depends on the release, the front-end, and the target architecture. In
the mainline compiler, I believe the C compiler does not have the
problem anymore.
Regards,
Martin