This is the mail archive of the
mailing list for the Cygwin project.
Re: [SOLVED] Re: What updates done after October 3 may affect gfortran built binaries?
- From: Edvardsen KÃre <kare dot edvardsen at uit dot no>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Wed, 16 Nov 2011 09:05:36 +0000
- Subject: Re: [SOLVED] Re: What updates done after October 3 may affect gfortran built binaries?
> > I helped Edvardsen to track this down off-list. It turns
> out that FLEXPART
> > is one of those huge number-crunching Fortran programs
> that's just jam-packed
> > with ginormous multi-dimensional arrays. The final linked
> executable had 3.38
> > GB of .bss space! So, it's not too surprising that it
> didn't load on 32-bit
> > Windows; and it's not, as I was worrying, any explicit bug
> in the compiler or
> > binutils (although it may be arguable that ld could be
> helpful if it issued
> > some kind of warning in these circumstances).
> Out of curiosity, how then was the OP ever able to make *any*
> version run?
I'm not sure of the exact pre-required settings I had when I compiled
FLEXPART to have a successful executable, but there seem to be various
default parameter settings in some of the FLEXPART include files that
will lead to some ginormous multi dimensional arrays.
I was pretty sure I did the exact same procedure when I compiled
FLEXPART later and got the non working executable, but if the .bss space
was too large, I must have done something else before. It's just that I
can't possibly think of anything I did different.
However, I'm determined to locate the problem, to advice the FLEXPART
developers. I don't want others to go through something similar.