aboutsummaryrefslogtreecommitdiff
path: root/memory_mapping.c
diff options
context:
space:
mode:
authorPeter Maydell <peter.maydell@linaro.org>2016-06-13 11:22:56 +0100
committerRiku Voipio <riku.voipio@linaro.org>2016-06-26 13:17:20 +0300
commit997f6ed3a1aee93b1b759ff12ad4ca64977c86f9 (patch)
tree83cf674943ff719acb92cbf57c6d1ee9d93b2779 /memory_mapping.c
parent1d48fdd9d84aab1bd32c1f70947932f5d90f92aa (diff)
downloadqemu-997f6ed3a1aee93b1b759ff12ad4ca64977c86f9.zip
qemu-997f6ed3a1aee93b1b759ff12ad4ca64977c86f9.tar.gz
qemu-997f6ed3a1aee93b1b759ff12ad4ca64977c86f9.tar.bz2
configure: Don't override ARCH=unknown if enabling TCI
At the moment if configure finds an unknown CPU it will set ARCH to 'unknown', and then later either bail out or set it to 'tci' (depending on whether the user passed configure the --enable-tcg-interpreter switch). This is unnecessarily confusing, because we could be using TCI in two cases: * a known host architecture (in which case ARCH is set to the actual host architecture, like 'i386') * an unknown host architecture (in which case ARCH is set to 'tci') so nothing can rely on ARCH=tci to mean "using TCI". Remove the line setting ARCH, so we leave it as "unknown", which is what the actual situation is. Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Reviewed-by: Richard Henderson <rth@twiddle.net> Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
Diffstat (limited to 'memory_mapping.c')
0 files changed, 0 insertions, 0 deletions