public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Caleb Tennis <caleb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new global use flag and a new category
Date: Thu, 26 Aug 2004 11:46:04 -0500	[thread overview]
Message-ID: <200408261146.04221.caleb@gentoo.org> (raw)
In-Reply-To: <200408261841.32114.carlo@gentoo.org>

> On Thursday 26 August 2004 18:02, Ciaran McCreesh wrote:
> > It'd help if you explained what the heck that actually did :)

When compiling a subdirectory, it basically lumps all of the headers and 
source into one big file and sends it to the compiler, which can then use all 
sorts of fancy optimizations since all of the compilation units are in that 
one file, vs. multiple files.  It makes compilation a LOT faster and produces 
much more optimized binaries, at the expense of needing much more space for 
temporary files during the compile.  Also, it doesn't always get tested 100% 
before a release, so sometimes an #include is missing which causes the 
compilation to fail.

Caleb

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-08-26 16:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 15:56 [gentoo-dev] new global use flag and a new category Carsten Lohrke
2004-08-26 16:02 ` Ciaran McCreesh
2004-08-26 16:41   ` Carsten Lohrke
2004-08-26 16:46     ` Caleb Tennis [this message]
2004-08-27 13:08 ` Mike Frysinger
2004-08-28 22:31   ` Carsten Lohrke
2004-08-29 17:44     ` Mike Frysinger
2004-08-29 18:10       ` Carsten Lohrke
2004-08-29 18:32         ` Mike Frysinger
2004-08-30 10:05           ` Paul de Vrieze
2004-08-28  9:58 ` Markus Nigbur
2004-08-29 19:42 ` Spider
2004-08-30  8:51   ` [gentoo-dev] " Duncan
2004-08-30 11:07     ` Mike Frysinger
2004-08-30 14:33   ` [gentoo-dev] " Carsten Lohrke
2004-09-01 20:47     ` William Hubbs

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=200408261146.04221.caleb@gentoo.org \
    --to=caleb@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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