From: Paolo Bonzini <pbonzini@redhat.com>
To: todd@fries.net
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] large memory requirements for translate.c a barrier
Date: Sat, 16 Mar 2013 09:14:29 +0100 [thread overview]
Message-ID: <514429E5.2010003@redhat.com> (raw)
In-Reply-To: <20130315192120.GF26815@fries.net>
Il 15/03/2013 20:21, Todd T. Fries ha scritto:
> PID USERNAME PRI NICE SIZE RES STATE WAIT TIME CPU COMMAND
> 28818 todd 64 0 1142M 53M onproc/0 - 2:01 17.24% cc1
>
> For systems with lower limits on user process memory, this prevents things
> from building.
>
> For systems with less physical ram, this presents lots of swapping just to
> build the source files.
>
> Is there any hints or hope of breaking translate.c up into a smaller file?
It's a GCC bug. We have worked around it in recent versions of QEMU;
what version are you trying to compile?
You can compile that file with "-O2 -fno-gcse".
Paolo
next prev parent reply other threads:[~2013-03-16 8:14 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 [this message]
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
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=514429E5.2010003@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@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).