On 06/29/2017 12:47 PM, Paolo Bonzini wrote:
On 29/06/2017 17:46, Thomas Huth wrote:
TCI is enabled only with a specific configure argument if your machine
is not supported by TCG. This would break _build_ configurations, not
user configurations. It's a remote possibility that users are building
their own QEMU, with TCI enabled, to work around a TCG bug. So we can
be more speedy in removing the code.
You never know ... it's unlikely, but there might be people around who
run configure with "--enable-tcg-interpreter" on purpose.
And they have never reported a bug? :) But I agree it's not a big deal.
Richard should decide.
Paolo
And why the
hurry for removing this? It's been around in the current shape since
years, so waiting for two more releases does not hurt, does it?
It is unlikely someone is using it for ARM aarch64 (see patch 5).
MTTCG was not in 2.9 but is now enabled by default on alpha/arm* since
February 2017 and on ppc64 since April 2017. Looking at the 6 different
bugs I show in the cover, I'm pretty sure no active developer but me
keep trying to use tci :p
Phil.
