From: Geert Uytterhoeven <geert@linux-m68k.org>
To: lancetag@luminet.net, linux-m68k@vger.kernel.org
Cc: linux-kbuild@vger.kernel.org
Subject: Re: eliminate -pipe from kernel compile
Date: Mon, 11 May 2009 08:02:16 +0200 [thread overview]
Message-ID: <10f740e80905102302gbed0737y61c31900564ca704@mail.gmail.com> (raw)
In-Reply-To: <20090511015831.GB15777@luminet.net>
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.
>
> Thoughts?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-11 6:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 1:58 eliminate -pipe from kernel compile Lance Tagliapietra
2009-05-11 6:02 ` Geert Uytterhoeven [this message]
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:
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=10f740e80905102302gbed0737y61c31900564ca704@mail.gmail.com \
--to=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