From: "Andreas Färber" <afaerber@suse.de>
To: "\"陳韋任 (Wei-Ren Chen)\"" <chenwj@iis.sinica.edu.tw>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1.3] build: compile translate.o at -O1 optimization
Date: Tue, 27 Nov 2012 17:24:52 +0100 [thread overview]
Message-ID: <50B4E954.9010000@suse.de> (raw)
In-Reply-To: <20121127134953.GA11770@cs.nctu.edu.tw>
Am 27.11.2012 14:49, schrieb 陳韋任 (Wei-Ren Chen):
> On Tue, Nov 27, 2012 at 02:45:07PM +0100, Gerd Hoffmann wrote:
>> On 11/27/12 14:24, Peter Maydell wrote:
>>> On 27 November 2012 08:34, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>> Some versions of GCC require insane (>2GB) amounts of memory
>>>> to compile translate.o. As a countermeasure, compile it
>>>> with -O1. This should fix the buildbot failure for
>>>> default_x86_64_fedora16.
>>>
>>> This is a well known bug in old gcc (ie fixed in 4.5, 4.6 and
>>> trunk a year ago). Use a newer gcc, or a 64 bit build system
>>> with a reasonable amount of RAM, or as a workaround apply some
>>> suitable compiler flags by passing configure
>>> '--extra-cflags=-fno-var-tracking'. This patch definitely
>>> shouldn't be applied as we shouldn't be hampering the majority
>>> for the benefit of old broken systems.
>>
>> It isn't that simple. It's Fedora 17 with gcc 4.7.2 which runs oom
>> while compiling translate.c
>
> Even apply Peter's suggestion? Do all gcc 4.7.2 on various platform
> have the same problem, or it only happen on Fedora 17.
I ran into the same problem with various versions of openSUSE in the
openSUSE Build Service where v1.2 built fine.
openSUSE Factory is using gcc 4.7.2, 12.2 4.7.1.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-11-27 16:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 8:34 [Qemu-devel] [PATCH 1.3] build: compile translate.o at -O1 optimization 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2012-11-27 8:36 Paolo Bonzini
2012-11-27 9:27 ` Wenchao Xia
2012-11-27 9:37 ` Paolo Bonzini
2012-11-27 12:09 ` Gerd Hoffmann
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=50B4E954.9010000@suse.de \
--to=afaerber@suse.de \
--cc=chenwj@iis.sinica.edu.tw \
--cc=kraxel@redhat.com \
--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).