public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/38788] gcc 4.4.0 20090109 - Configure with "--enable-intermodule" breaks build
Date: Fri, 09 Jan 2009 22:16:00 -0000	[thread overview]
Message-ID: <20090109221616.18196.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38788-13830@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from rob1weld at aol dot com  2009-01-09 22:16 -------
(In reply to comment #3)
> You told the compiler to compile everything at the same time what do
> you expect to cause out of memory issues?

It could create temporary files (like qsort) and shrink the size of
the file (by optimizing) until it had done what it could. It could
then cut the tree in half (find two "unions of functions" connected
by a single point) and do each half with a single jump from one
section to the other.

If the _only_ thing it can do is "grab every file in the directory"
then it will fail in many of gcc's directories and is unlikely ever
to complete a build of all languanges, let alone just "C".

I did not expect that "-combine" would be little better than cat'ting the
source files together and compiling them (as we do that a fair bit already).

Rob


-- 


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


  parent reply	other threads:[~2009-01-09 22:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 21:09 [Bug bootstrap/38788] New: " rob1weld at aol dot com
2009-01-09 21:12 ` [Bug bootstrap/38788] " pinskia at gcc dot gnu dot org
2009-01-09 21:23 ` rob1weld at aol dot com
2009-01-09 21:29 ` pinskia at gcc dot gnu dot org
2009-01-09 22:16 ` rob1weld at aol dot com [this message]
2009-01-09 22:40 ` pinskia at gcc dot gnu dot org
2009-01-10  5:56 ` rob1weld at aol dot com
2009-01-13  0:31 ` pinskia at gcc dot gnu dot org
2009-01-13 14:58 ` rob1weld at aol dot com
2009-01-13 15:09 ` jakub at gcc dot gnu dot org
     [not found] <bug-38788-4@http.gcc.gnu.org/bugzilla/>
2010-12-09 17:56 ` gseanmcg at gmail dot com
2012-02-03 23:13 ` pinskia 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=20090109221616.18196.qmail@sourceware.org \
    --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).