From: Helge Deller <deller@gmx.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] configure: Automatically fall back to TCI on non-release architectures
Date: Thu, 4 Apr 2019 20:57:30 +0200 [thread overview]
Message-ID: <20190404185730.GA22512@ls3530.dellerweb.de> (raw)
If a non-release architecture is found, and it's known that there is no
native TCG support for that CPU, automatically fall back to the TCI
implementation instead of requesting the user to run configure again
with the --enable-tcg-interpreter option.
This change simplifies building qemu in automatic build environments
(like in my case the debian buildds) because one does not need to
special case on the architectures.
Signed-off-by: Helge Deller <deller@gmx.de>
diff --git a/configure b/configure
index 1c563a7027..8fe4fc84d8 100755
--- a/configure
+++ b/configure
@@ -769,8 +769,10 @@ case "$cpu" in
cross_cc_sparc=$host_cc
;;
*)
- # This will result in either an error or falling back to TCI later
+ # Fall back to TCI on unsupported CPUs
ARCH=unknown
+ echo "Unsupported '$cpu' CPU found. Will use TCG with TCI (experimental)."
+ tcg_interpreter="yes"
;;
esac
if test -z "$ARCH"; then
@@ -1855,16 +1857,6 @@ if ! compile_prog ; then
error_exit "\"$cc\" cannot build an executable (is your linker broken?)"
fi
-# Now we have handled --enable-tcg-interpreter and know we're not just
-# printing the help message, bail out if the host CPU isn't supported.
-if test "$ARCH" = "unknown"; then
- if test "$tcg_interpreter" = "yes" ; then
- echo "Unsupported CPU = $cpu, will use TCG with TCI (experimental)"
- else
- error_exit "Unsupported CPU = $cpu, try --enable-tcg-interpreter"
- fi
-fi
-
# Consult white-list to determine whether to enable werror
# by default. Only enable by default for git builds
if test -z "$werror" ; then
next reply other threads:[~2019-04-04 18:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 18:57 Helge Deller [this message]
2019-04-04 19:24 ` [Qemu-devel] [PATCH] configure: Automatically fall back to TCI on non-release architectures Philippe Mathieu-Daudé
2019-04-05 7:14 ` Helge Deller
2019-04-05 7:14 ` Helge Deller
2019-04-05 1:34 ` Peter Maydell
2019-04-05 1:34 ` Peter Maydell
2019-04-05 7:56 ` Helge Deller
2019-04-05 7:56 ` Helge Deller
2019-04-05 8:26 ` Daniel P. Berrangé
2019-04-05 8:26 ` Daniel P. Berrangé
2019-04-05 9:02 ` Helge Deller
2019-04-05 9:02 ` Helge Deller
2019-04-05 9:10 ` Philippe Mathieu-Daudé
2019-04-05 9:10 ` Philippe Mathieu-Daudé
2019-04-05 9:13 ` Peter Maydell
2019-04-05 9:13 ` Peter Maydell
2019-04-05 9:15 ` Daniel P. Berrangé
2019-04-05 9:15 ` Daniel P. Berrangé
2019-04-05 8:47 ` Philippe Mathieu-Daudé
2019-04-05 8:47 ` Philippe Mathieu-Daudé
2019-04-05 9:02 ` Daniel P. Berrangé
2019-04-05 9:02 ` Daniel P. Berrangé
2019-04-05 9:16 ` Philippe Mathieu-Daudé
2019-04-05 9:16 ` Philippe Mathieu-Daudé
2019-04-09 19:46 ` Stefan Weil
2019-04-09 19:46 ` Stefan Weil
2019-04-09 20:39 ` Richard Henderson
2019-04-09 20:39 ` Richard Henderson
2019-04-10 6:17 ` Stefan Weil
2019-04-10 6:17 ` Stefan Weil
2019-04-11 6:21 ` Richard Henderson
2019-04-11 6:21 ` Richard Henderson
2019-04-10 6:07 ` Thomas Huth
2019-04-10 6:07 ` Thomas Huth
2019-04-10 6:24 ` Stefan Weil
2019-04-10 6:24 ` Stefan Weil
2019-04-10 8:22 ` Thomas Huth
2019-04-10 8:22 ` Thomas Huth
2019-04-10 19:22 ` Stefan Weil
2019-04-10 19:22 ` Stefan Weil
2019-04-10 7:48 ` Thomas Huth
2019-04-10 7:48 ` Thomas Huth
2019-04-06 8:59 ` Richard Henderson
2019-04-06 8:59 ` Richard Henderson
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=20190404185730.GA22512@ls3530.dellerweb.de \
--to=deller@gmx.de \
--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).