From: walt <w41ter@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: git commit c832e3de chokes gcc-4.5.2 (out of memory error)
Date: Sat, 19 Mar 2011 09:06:31 -0700 [thread overview]
Message-ID: <im2kad$f2o$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTimi94FaVUT6o0xnsjKb4gjKdVDVPVZ_g6mYr2Qz@mail.gmail.com>
On 03/18/2011 03:44 PM, Peter Maydell wrote:
> On 18 March 2011 23:31, walt<w41ter@gmail.com> wrote:
>> The following commit has a strange side-effect on gcc-4.5.2:
>> The new code in 'target-i386/translate.c' compiles just fine with gcc-4.4.4,
>> using less than 1GB of RAM, but gcc-4.5.2 uses the whole GB and then fills
>> up 2GB of swap space in addition while the machine grinds slowly to a halt.
>
> I'm wondering whether this is
> https://bugs.launchpad.net/gcc-linaro/+bug/714921
> again (an upstream gcc bug, fix in-progress).
>
>> I'm hoping someone here might know how to find the source of the problem
>> so I can add some helpful details to my bug report.
>
> 1. If you compile with -fno-var-tracking does it still use lots
> of memory?
That flag fixes the memory problem, so my bug must be the same, I think.
> 2. (for the ludicrously enthusiastic only) build a gcc with the patches
> listed in that bug report and see if the problem goes away...
I fetched the patch and found that it doesn't apply cleanly to the heavily
patched gentoo sources :(
Many thanks for the excellent clue.
prev parent reply other threads:[~2011-03-19 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 22:31 [Qemu-devel] git commit c832e3de chokes gcc-4.5.2 (out of memory error) walt
2011-03-18 22:44 ` Peter Maydell
2011-03-19 16:06 ` walt [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='im2kad$f2o$1@dough.gmane.org' \
--to=w41ter@gmail.com \
--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 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.