public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fwi at inducks dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50924] Attempt to allocate negative amount of memory. Possible integer overflow
Date: Mon, 31 Oct 2011 08:43:00 -0000	[thread overview]
Message-ID: <bug-50924-4-56DiJED57V@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50924-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50924

--- Comment #4 from fwi at inducks dot org 2011-10-31 08:43:23 UTC ---
Actually contrary to what I wrote my system is 64 bit (I clicked on "edit" on
the top right and somehow the system sent a message that I was starting to
write). 


Still when I run my program on a 64-bit machine with 16 Gb of RAM (under
CentOS), I could fill up 96% of the RAM with just one big array. I don't really
understand why such restriction is enforced.


      parent reply	other threads:[~2011-10-31  8:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-30 17:57 [Bug fortran/50924] New: " fwi at inducks dot org
2011-10-30 18:52 ` [Bug fortran/50924] " fwi at inducks dot org
2011-10-30 18:55 ` kargl at gcc dot gnu.org
2011-10-30 21:55 ` rguenth at gcc dot gnu.org
2011-10-31  8:43 ` fwi at inducks dot org [this message]

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=bug-50924-4-56DiJED57V@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).