From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: peter.maydell@linaro.org, Bruce Rogers <brogers@suse.com>,
qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1.3] build: compile translate.o with -fno-gcse option on GCC 4.6.x and 4.7.[012]
Date: Wed, 28 Nov 2012 18:27:45 +0100 [thread overview]
Message-ID: <50B64991.2020309@suse.de> (raw)
In-Reply-To: <1354092023-10897-1-git-send-email-pbonzini@redhat.com>
Am 28.11.2012 09:40, schrieb Paolo Bonzini:
> These 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
> this 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>
Tested-by: Andreas Färber <afaerber@suse.de>
> ---
> Makefile.target | 3 +++
> configure | 16 ++++++++++++++++
> 2 files changed, 19 insertions(+)
>
> diff --git a/Makefile.target b/Makefile.target
> index 8b658c0..927347b 100644
> --- a/Makefile.target
> +++ b/Makefile.target
> @@ -143,6 +143,9 @@ GENERATED_HEADERS += hmp-commands.h qmp-commands-old.h
>
> endif # CONFIG_SOFTMMU
>
> +# Workaround for http://gcc.gnu.org/PR55489, see configure.
> +%/translate.o: QEMU_CFLAGS += $(TRANSLATE_OPT_CFLAGS)
> +
> nested-vars += obj-y
>
> # This resolves all nested paths, so it must come last
> diff --git a/configure b/configure
> index 780b19a..994f731 100755
> --- a/configure
> +++ b/configure
> @@ -1183,6 +1183,21 @@ for flag in $gcc_flags; do
> fi
> done
>
> +# 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.6.x and 4.7.x. It is fixed in
> +# 4.7.3 and 4.8.0. We should be able to delete this at the end of 2013.
> +cat > $TMPC << EOF
> +#if __GNUC__ == 4 && (__GNUC_MINOR__ == 6 || (__GNUC_MINOR__ == 7 && __GNUC_PATCHLEVEL__ <= 2))
FWIW this line looks overly long.
> +int main(void) { return 0; }
> +#else
> +#error No bug in this compiler.
Interesting logic. :)
Andreas
> +#endif
> +EOF
> +if compile_prog "-Werror -fno-gcse" "" ; then
> + TRANSLATE_OPT_CFLAGS=-fno-gcse
> +fi
> +
> if test "$static" = "yes" ; then
> if test "$pie" = "yes" ; then
> echo "static and pie are mutually incompatible"
> @@ -3662,6 +3677,7 @@ echo "LIBS_TOOLS+=$libs_tools" >> $config_host_mak
> echo "EXESUF=$EXESUF" >> $config_host_mak
> echo "LIBS_QGA+=$libs_qga" >> $config_host_mak
> echo "POD2MAN=$POD2MAN" >> $config_host_mak
> +echo "TRANSLATE_OPT_CFLAGS=$TRANSLATE_OPT_CFLAGS" >> $config_host_mak
>
> # generate list of library paths for linker script
>
>
--
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-28 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 8:40 [Qemu-devel] [PATCH v3 1.3] build: compile translate.o with -fno-gcse option on GCC 4.6.x and 4.7.[012] Paolo Bonzini
2012-11-28 17:27 ` Andreas Färber [this message]
2012-11-28 21:37 ` Anthony Liguori
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=50B64991.2020309@suse.de \
--to=afaerber@suse.de \
--cc=brogers@suse.com \
--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 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.