qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, kraxel@redhat.com
Subject: [Qemu-devel] [PATCH v2 1.3] build: compile translate.o with -fno-gcse option
Date: Tue, 27 Nov 2012 17:21:03 +0100	[thread overview]
Message-ID: <1354033263-32748-1-git-send-email-pbonzini@redhat.com> (raw)

Some versions of GCC require insane (>2GB) amounts of memory to compile
translate.o.  As a countermeasure, disable the culprit optimization pass.
This should fix the buildbot failure for default_x86_64_fedora16.
Anyway is a good thing to do because people will try to compile 1.3 with
less than 2GB of memory and complain.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
 Makefile.target | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Makefile.target b/Makefile.target
index 8b658c0..d38bb58 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -143,6 +143,12 @@ GENERATED_HEADERS += hmp-commands.h qmp-commands-old.h
 
 endif # CONFIG_SOFTMMU
 
+# Workaround for http://gcc.gnu.org/PR55489.  Happens with -fPIE/-fPIC
+# and large functions that use global variables.  The bug is in all
+# releases of GCC, but it became particularly acute in 4.7.x.  We
+# should be able to delete this at the end of 2013.
+%/translate.o: QEMU_CFLAGS += -fno-gcse
+
 nested-vars += obj-y
 
 # This resolves all nested paths, so it must come last
-- 
1.8.0

             reply	other threads:[~2012-11-27 16:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 16:21 Paolo Bonzini [this message]
2012-11-27 16:24 ` [Qemu-devel] [PATCH v2 1.3] build: compile translate.o with -fno-gcse option Alexander Graf
2012-11-27 16:30   ` Paolo Bonzini
2012-11-27 18:17     ` Stefan Weil
2012-11-28  7:29       ` Paolo Bonzini
2012-11-28  2:01 ` 陳韋任 (Wei-Ren Chen)
2012-11-28  2:34   ` Wenchao Xia
2012-11-28 10:47 ` 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=1354033263-32748-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kraxel@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).