All of
 help / color / mirror / Atom feed
From: Lance Tagliapietra <>
Subject: eliminate -pipe from kernel compile
Date: Sun, 10 May 2009 20:58:33 -0500	[thread overview]
Message-ID: <> (raw)


I was noticing that kernel compiling is set up to have gcc pipe data from one pass to another, instead of using 
temporary files.  On a memory constrained environment, this may not be the best idea (or at least I'd like to
explore that idea).  Instead of loading the assember, and having immediately being swapped out while the cc1 pass 
runs, it may make more sense to have the temp files being written, instead of the swap in and out, when compiling 
the various objects of the kernel.

So, simply pulling out the -pipe from the compiler flag list didn't see to have the desired effect.  I'm afraid I'm 
still missing something.  I'm still observing the assembler being loaded.




             reply	other threads:[~2009-05-11  2:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11  1:58 Lance Tagliapietra [this message]
2009-05-11  6:02 ` eliminate -pipe from kernel compile Geert Uytterhoeven
2009-05-11  6:02   ` Geert Uytterhoeven
2009-05-13  0:38   ` Sam Ravnborg
2009-05-13  0:38     ` Sam Ravnborg
2009-05-14  3:12     ` Lance Tagliapietra

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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.