From: Dave Korn <dave.korn.cygwin@gmail.com>
To: cygwin@cygwin.com
Subject: [SOLVED] Re: What updates done after October 3 may affect gfortran built binaries?
Date: Tue, 15 Nov 2011 15:54:00 -0000 [thread overview]
Message-ID: <4EC28AE7.70600@gmail.com> (raw)
In-Reply-To: <1320840871.13045.51.camel@kare-desktop>
On 09/11/2011 12:15, Edvardsen KÃ¥re wrote:
> This is again related to the failure of execution of a gfortran built
> binary ("cannot execute binary", see thread
> http://cygwin.com/ml/cygwin/2011-11/msg00034.html )
>
> In short, the main problem is that I can't build a successful binary
> from the FLEXPART fortran code
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).
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-11-15 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 12:15 Edvardsen Kåre
2011-11-09 13:07 ` Marco Atzeri
2011-11-15 15:54 ` Dave Korn [this message]
2011-11-15 16:21 ` [SOLVED] " Ryan Johnson
2011-11-15 22:55 ` Dave Korn
2011-11-16 9:06 Edvardsen Kåre
2011-11-16 11:30 Edvardsen Kåre
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=4EC28AE7.70600@gmail.com \
--to=dave.korn.cygwin@gmail.com \
--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).