public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rth@gcc.gnu.org
To: 133574@bugs.debian.org, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	pavel@atrey.karlin.mff.cuni.cz
Subject: Re: other/9081: gcc doesn't diagnose, that the compiler exceeds a compiler limit
Date: Sun, 26 Jan 2003 09:43:00 -0000	[thread overview]
Message-ID: <20030126094006.25199.qmail@sources.redhat.com> (raw)

Synopsis: gcc doesn't diagnose, that the compiler exceeds a compiler limit

State-Changed-From-To: open->closed
State-Changed-By: rth
State-Changed-When: Sun Jan 26 09:39:58 2003
State-Changed-Why:
    This isn't a compiler problem.  There is no compiler limit that
    has been exceeded.  Indeed, the executable generated looks fine.
    The kernel, however, is refusing to map the very large bss
    segment.  Perhaps your ulimit is set too low?  Perhaps you
    don't have enough VM to satisfy the request?
    
    In fact, if I enable a 2G swap file, and link the program
    statically, then it runs just fine.
    
    (If you don't link statically, then ld.so crashes.  I suspect
    a different kernel bug, in that it's not adjusting where it
    maps ld.so based on the large bss segment.)

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9081


             reply	other threads:[~2003-01-26  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26  9:43 rth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-28  2:46 Peter Bergner
2003-01-26 20:06 Pavel Machek
2002-12-28  6:06 Matthias Klose

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=20030126094006.25199.qmail@sources.redhat.com \
    --to=rth@gcc.gnu.org \
    --cc=133574@bugs.debian.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=pavel@atrey.karlin.mff.cuni.cz \
    /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).