public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Lance Tagliapietra <lancetag@luminet.net>
Cc: linux-m68k@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: eliminate -pipe from kernel compile
Date: Wed, 13 May 2009 02:38:29 +0200	[thread overview]
Message-ID: <20090513003829.GA13155@uranus.ravnborg.org> (raw)
In-Reply-To: <10f740e80905102302gbed0737y61c31900564ca704@mail.gmail.com>

On Mon, May 11, 2009 at 08:02:16AM +0200, Geert Uytterhoeven wrote:
> Added linux-kbuild
> 
> On Mon, May 11, 2009 at 03:58, Lance Tagliapietra <lancetag@luminet.net> wrote:
> > 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.

1) How did you "pulling out the -pipe from the compiler flag list"?
Please show this as a patch.

2) Did you verify that -pipe was used before and no more after your
   changes?
   Hint - use "make V=1" to see all command line options to gcc

	Sam

  reply	other threads:[~2009-05-13  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090511015831.GB15777@luminet.net>
2009-05-11  6:02 ` eliminate -pipe from kernel compile Geert Uytterhoeven
2009-05-13  0:38   ` Sam Ravnborg [this message]
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:
  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=20090513003829.GA13155@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=geert@linux-m68k.org \
    --cc=lancetag@luminet.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.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