public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/378] [AIX] gcc cannot compile huge c file
Date: Tue, 01 Apr 2014 16:02:00 -0000	[thread overview]
Message-ID: <bug-378-4-ydowoJkTDm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-378-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from David Edelsohn <dje at gcc dot gnu.org> ---
Recent releases of GCC are built with linker options to allow larger data
section. Are the user process limits (ulimit) set large enough?  One could
rebuild GCC cc1 and cc1plus with even larger -bmaxdata value (or patch the
binary with a larger value), but it's not clear which limit is hit.


  parent reply	other threads:[~2014-04-01 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-378-4@http.gcc.gnu.org/bugzilla/>
2014-04-01 15:46 ` Doug at CSFi dot com
2014-04-01 16:02 ` dje at gcc dot gnu.org [this message]
2014-04-01 18:44 ` Doug at CSFi dot com
2014-04-03 14:00 ` dje at gcc dot gnu.org
     [not found] <bug-378-4755@http.gcc.gnu.org/bugzilla/>
2006-02-24 17:54 ` ska at resqnet dot com
2007-03-28  8:32 ` satyaakam at yahoo dot co dot in
     [not found] <20000705135602.378.tsawan@us.ibm.com>
2004-12-19 20:37 ` dje at gcc dot gnu dot org
2005-01-10  9:53 ` coudert at clipper dot ens dot fr

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-378-4-ydowoJkTDm@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).