All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1.3] build: compile translate.o at -O1 optimization
Date: Tue, 27 Nov 2012 10:37:11 +0100	[thread overview]
Message-ID: <50B489C7.7080608@redhat.com> (raw)
In-Reply-To: <50B48790.8030705@linux.vnet.ibm.com>

Il 27/11/2012 10:27, Wenchao Xia ha scritto:
>   In tcg case I think translate.o will influent performance obviously,
> how about adding an option "fast-build" to use -O1 for it by default.
> If you agree I will adding that after this patch upstream which fix
> build bot failure quickly.

This is not about having a fast or slow build, it's about not requiring
a ludicrous amount of memory...  Besides, translate.c is usually not too
high in the profiles.  Most of the time is spent _executing_
JIT-translated code, not translating it.

Note that there is probably one or two GCC options that can be
fine-tuned to avoid the explosion instead of just -O1 vs. -O2.  If you
have an affected machine (F18) you can help by compiling translate.c
with -O2 -ftime-report.  I planned to do this today, but I first need to
install a F18 virtual machine.

Paolo

  reply	other threads:[~2012-11-27  9:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27  8:36 [Qemu-devel] [PATCH 1.3] build: compile translate.o at -O1 optimization Paolo Bonzini
2012-11-27  9:27 ` Wenchao Xia
2012-11-27  9:37   ` Paolo Bonzini [this message]
2012-11-27 12:09     ` Gerd Hoffmann
  -- strict thread matches above, loose matches on Subject: below --
2012-11-27  8:34 Paolo Bonzini
2012-11-27 13:24 ` Peter Maydell
2012-11-27 13:45   ` Gerd Hoffmann
2012-11-27 13:46     ` Peter Maydell
2012-11-27 14:10       ` Paolo Bonzini
2012-11-27 13:49     ` 陳韋任 (Wei-Ren Chen)
2012-11-27 15:05       ` Paolo Bonzini
2012-11-27 16:24       ` Andreas Färber
2012-11-27 15:53 ` Avi Kivity
2012-11-27 16:02   ` Paolo Bonzini
2012-11-27 16:49   ` Markus Armbruster
2012-11-27 16:55     ` Paolo Bonzini

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=50B489C7.7080608@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xiawenc@linux.vnet.ibm.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.