From: "Edvardsen Kåre" <kare.edvardsen@uit.no>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [SOLVED] Re: What updates done after October 3 may affect gfortran built binaries?
Date: Wed, 16 Nov 2011 09:06:00 -0000 [thread overview]
Message-ID: <1321434334.6778.22.camel@kare-desktop> (raw)
> > 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?
>
> Ryan
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.
Kåre
next reply other threads:[~2011-11-16 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 9:06 Edvardsen Kåre [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-16 11:30 Edvardsen Kåre
2011-11-09 12:15 Edvardsen Kåre
2011-11-15 15:54 ` [SOLVED] " Dave Korn
2011-11-15 16:21 ` Ryan Johnson
2011-11-15 22:55 ` Dave Korn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1321434334.6778.22.camel@kare-desktop \
--to=kare.edvardsen@uit.no \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).