public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "klaus dot kusche at inode dot at" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/22341] Interix: gcj out of virtual mem during libgcj make
Date: Thu, 07 Jul 2005 14:38:00 -0000	[thread overview]
Message-ID: <20050707143817.20136.qmail@sourceware.org> (raw)
In-Reply-To: <20050707094458.22341.klaus.kusche@inode.at>


------- Additional Comments From klaus dot kusche at inode dot at  2005-07-07 14:38 -------
But on supported configurations (and afaik interix is one of them), an out-of-
the-box gcc build (incl. libgcj) should not be guranteed to fail.

This is no physical limit (memory size, swap space, ...), we tried on several 
different systems, all failed in the same way.

It is a fundamental architectural problem: There is a 2 GB virtual address 
space limit for each process in Windows, and in combination with the way 
windows loads DLLs etc., gcc will hit this limit when building libgcj with the 
default settings, no matter how large the hardware is.

-- 


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


  parent reply	other threads:[~2005-07-07 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07  9:45 [Bug libgcj/22341] New: " klaus dot kusche at inode dot at
2005-07-07 12:58 ` [Bug libgcj/22341] " pinskia at gcc dot gnu dot org
2005-07-07 13:03 ` pinskia at gcc dot gnu dot org
2005-07-07 14:38 ` klaus dot kusche at inode dot at [this message]
     [not found] <bug-22341-8172@http.gcc.gnu.org/bugzilla/>
2012-01-11 14:09 ` rguenth at gcc dot gnu.org

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=20050707143817.20136.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).