From: nello martuscielli <ppc.addon@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] Re: qemu-0.14.0 doesn't compile on ppc32
Date: Tue, 22 Feb 2011 01:56:49 +0100 [thread overview]
Message-ID: <AANLkTi=gNJM1Y69=bbcovc1SLGo5nYckoa0_vM56vEn9@mail.gmail.com> (raw)
In-Reply-To: <4D621DE8.60506@redhat.com>
On Mon, Feb 21, 2011 at 9:10 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 02/20/2011 06:32 PM, Peter Maydell wrote:
>>
>> On 20 February 2011 16:56, Aurelien Jarno<aurelien@aurel32.net> wrote:
>>>
>>> On Sun, Feb 20, 2011 at 03:01:12PM +0100, nello martuscielli wrote:
>>>>
>>>> CC x86_64-softmmu/translate.o
>>>> {standard input}: Assembler messages:
>>>> {standard input}:11903788: Warning: end of file not at end of a line;
>>>> newline inserted
>>>> gcc: Internal error: Killed (program cc1)
>>
>>> It is most likely a compiler/setup issue. My guess your machine got out
>>> of memory, and the OOM killer killed cc1. Try adding more memory and/or
>>> swap, it should work.
>>
>> Some of qemu's code does seem to trigger rather excessive memory
>> use by gcc; for instance we've had problems with memory usage
>> building for ARM with gcc of target-sparc/translate.c wanting
>> gigabytes of RAM with some compiler flags:
>> https://bugs.launchpad.net/gcc-linaro/+bug/714921
>>
>> I suspect it's all those large switch statements...
>
> It's on my todo list to report it to GCC, since this memory-hog behavior is
> a GCC regression.
>
> Paolo
>
compiling with -fno-var-tracking i just succesfully built it without
any out of memory error.
So it seems it's possible to compile qemu on ppc32 without a
ridiculous high amount of ram with gcc-4.5.2.
next prev parent reply other threads:[~2011-02-22 0:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 14:01 [Qemu-devel] qemu-0.14.0 doesn't compile on ppc32 nello martuscielli
2011-02-20 16:56 ` Aurelien Jarno
2011-02-20 17:02 ` malc
2011-02-20 23:34 ` nello martuscielli
2011-02-21 0:15 ` malc
2011-02-20 17:32 ` Peter Maydell
2011-02-21 8:10 ` [Qemu-devel] " Paolo Bonzini
2011-02-22 0:56 ` nello martuscielli [this message]
2011-03-14 10:23 ` Peter Maydell
2011-03-14 10:33 ` Stefan Hajnoczi
2011-03-14 19:14 ` Blue Swirl
2011-03-14 11:17 ` Paolo Bonzini
2011-02-20 23:32 ` [Qemu-devel] " nello martuscielli
2011-02-20 17:01 ` malc
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='AANLkTi=gNJM1Y69=bbcovc1SLGo5nYckoa0_vM56vEn9@mail.gmail.com' \
--to=ppc.addon@gmail.com \
--cc=aurelien@aurel32.net \
--cc=pbonzini@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).