qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] build: allow turning off debuginfo
Date: Fri, 24 Feb 2012 18:52:19 +0100	[thread overview]
Message-ID: <4F47CE53.8020004@redhat.com> (raw)
In-Reply-To: <CAFEAcA-f=OZVoR9wOjjEdxOyRVUCZH7fUgxBxP6UCy0XX9JAkw@mail.gmail.com>

On 02/24/12 12:16, Peter Maydell wrote:
> On 24 February 2012 10:39, Gerd Hoffmann <kraxel@redhat.com> wrote:
>> On 02/08/12 13:54, Gerd Hoffmann wrote:
>>> This patch adds --{enable,disable}-debug-info switches to configure
>>> which allows to include/exclude the '-g' switch on the gcc & ld
>>> command lines.  Not building debug info reduces ressource usage
>>> (especially disk) alot and is quite useful for test builds.
>>
>> ping?
> 
> We've had this suggested before, haven't we? I quite like the
> existing "just build with -g and strip it later" approach...
> is the resource usage change really that significant?

Disk usage is factor ten:

[kraxel@mort qemu]$ du -sh build-*
1,7G    build-debug
173M    build-nodebug

Build time is factor two:

[build-debug]
7263.45user 805.85system 3:11:03elapsed 70%CPU (0avgtext+0avgdata
1782576maxresident)k
72784880inputs+13340840outputs (1273066major+29668783minor)pagefaults 0swaps

[build-nodebug]
5329.72user 320.46system 1:34:26elapsed 99%CPU (0avgtext+0avgdata
1542848maxresident)k
116000inputs+755248outputs (255major+16535699minor)pagefaults 0swaps

cheers,
  Gerd

  reply	other threads:[~2012-02-24 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 12:54 [Qemu-devel] [PATCH] build: allow turning off debuginfo Gerd Hoffmann
2012-02-24 10:39 ` Gerd Hoffmann
2012-02-24 11:16   ` Peter Maydell
2012-02-24 17:52     ` Gerd Hoffmann [this message]
2012-02-24 19:46     ` Anthony Liguori

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=4F47CE53.8020004@redhat.com \
    --to=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).