From: Tim Prince <timothyprince@sbcglobal.net>
To: deepan@novaglobal.com.sg
Cc: gcc-help@gcc.gnu.org
Subject: Re: memory problem
Date: Thu, 09 Nov 2006 13:32:00 -0000 [thread overview]
Message-ID: <45532DD3.2030806@sbcglobal.net> (raw)
In-Reply-To: <1163048394.2744.7.camel@localhost.localdomain>
Deepan wrote:
> Hi,
> My fortran code compiles fine if i use arrays of size less that 4 GB.
> When i increase the array size to more that 4 GB, the compilation fails
> with the following error. I am running this on 32GB RAM machine.
>
> $ g77 -O3 MAIN.o write_output.o read_population.o write_population.o
> collide.o initial_conditions.o stream.o communicate.o -o lbm.x
> -I/usr/local/include -L/usr/local/lib -lmpich -lpthread -lrt
> MAIN.o(.text+0x7a): In function `MAIN__':
> : relocation truncated to fit: R_X86_64_PC32 directions_
> read_population.o(.text+0x252): In function `read_population__':
> I guess there must me some option to g77, that will let the program
> use more than 4 GB of memory.
x86_64 binutils don't support larger static objects. You should have no
trouble using more memory, just not in a single static object. As g77
doesn't support allocatable arrays nor Cray pointers, you would have to
change compilers (e.g. to gfortran) to use either of those methods.
Remember that g77 support had dwindled before x86_64 was released.
next prev parent reply other threads:[~2006-11-09 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 4:59 Deepan
2006-11-09 13:32 ` Tim Prince [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-13 17:39 lrtaylor
2005-01-13 17:32 xuejun gu
2005-01-13 17:39 ` Eljay Love-Jensen
[not found] <20040913111103.77851.qmail@web52901.mail.yahoo.com>
2004-09-13 11:48 ` Ron Michael Khu
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=45532DD3.2030806@sbcglobal.net \
--to=timothyprince@sbcglobal.net \
--cc=deepan@novaglobal.com.sg \
--cc=gcc-help@gcc.gnu.org \
--cc=tprince@myrealbox.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).