All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Default value for FULL_OPTIMIZATION
Date: Wed, 03 Feb 2016 20:57:58 +0000	[thread overview]
Message-ID: <1454533078.7421.57.camel@pbcl.net> (raw)
In-Reply-To: <CAMKF1sqevO99mD2V1xxZEa7--LX9vctuFebLc59fOej3xnjkhA@mail.gmail.com>

On Wed, 2016-02-03 at 12:51 -0800, Khem Raj wrote:
> On Wed, Feb 3, 2016 at 12:48 PM, Phil Blundell <pb@pbcl.net> wrote:
> > On Tue, 2016-02-02 at 22:17 -0800, Khem Raj wrote:
> >> -pipe does speed up build time so its an optimization.
> >
> > How much does it really speed it up by?  I seem to recall the effect was
> > fairly negligible, but maybe I am remembering that wrong.
> 
> it does not create files for intermediate objects so if you have slow
> media it can be significant
> but if you have SSDs then it might be diminished.

The files go in /tmp though, right?  Even if that isn't a tmpfs, which I
think it is on almost all systems nowadays, they will almost certainly
just sit in the buffer cache and never actually get written to the
disk. 

p.




  parent reply	other threads:[~2016-02-03 20:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 13:26 Default value for FULL_OPTIMIZATION Pascal Bach
2016-02-02 14:26 ` Mike Looijmans
2016-02-02 16:23   ` Pascal Bach
2016-02-02 14:47 ` Richard Purdie
2016-02-02 20:52 ` Phil Blundell
2016-02-03  6:17   ` Khem Raj
2016-02-03 20:48     ` Phil Blundell
2016-02-03 20:51       ` Khem Raj
2016-02-03 20:54         ` Burton, Ross
2016-02-03 20:57         ` Phil Blundell [this message]
2016-02-03 20:59           ` Khem Raj
2016-02-03 21:08             ` Phil Blundell
2016-02-03 22:37               ` Khem Raj
2016-02-04 12:56             ` Mike Looijmans

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=1454533078.7421.57.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.