From: "Andreas Färber" <afaerber@suse.de>
To: todd@fries.net
Cc: Alexander Graf <agraf@suse.de>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-ppc <qemu-ppc@nongnu.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] large memory requirements for translate.c a barrier
Date: Tue, 19 Mar 2013 16:18:19 +0100 [thread overview]
Message-ID: <514881BB.7070808@suse.de> (raw)
In-Reply-To: <20130315192120.GF26815@fries.net>
Am 15.03.2013 20:21, schrieb Todd T. Fries:
> Is there any hints or hope of breaking translate.c up into a smaller file?
You don't specify which version you're talking about (git?) and don't
mention which translate.c file either.
The longest-building one I am aware of was target-ppc/translate.c, and I
have just recently split some code out of it to reduce its size.
But this is an Open Source project, so you too can look at the code and
make suggestions of how to split, e.g., target-ppc/translate_init.c off
from target-ppc/translate.c or even better send patches for improvement.
Short of that, you can configure with --target-list= to only build the
targets you actually need.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-03-19 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 19:21 [Qemu-devel] large memory requirements for translate.c a barrier Todd T. Fries
2013-03-16 8:14 ` Paolo Bonzini
2013-03-19 15:05 ` qemu-devel
2013-03-21 7:53 ` qemu-devel
2013-03-21 8:25 ` Paolo Bonzini
2013-03-22 7:08 ` qemu-devel
2013-03-22 7:30 ` 陳韋任 (Wei-Ren Chen)
2013-03-22 15:19 ` qemu-devel
2013-03-22 15:28 ` Peter Maydell
2013-03-22 9:34 ` Paolo Bonzini
2013-03-19 15:18 ` Andreas Färber [this message]
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=514881BB.7070808@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=todd@fries.net \
/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).