Now that the sparc tcg backend has finally had guest-base support added, we can declare that it is mandatory. This lets us (a) drop the configure script support for a host CPU type not actually supporting guest-base (b) remove the now unnecessary compile time check for whether the TCG backend supports guest-base.
A possible future Part II would be to make guest-base mandatory for the -user targets (rather than merely the default, as now). That is, we could drop CONFIG_USER_GUEST_BASE. Does anybody have a practical use case for the --disable-guest-base configuration? Peter Maydell (2): configure: Remove unnecessary host_guest_base code tcg: Remove TCG_TARGET_HAS_GUEST_BASE define configure | 31 ++----------------------------- tcg/arm/tcg-target.h | 2 -- tcg/hppa/tcg-target.h | 2 -- tcg/i386/tcg-target.h | 2 -- tcg/ia64/tcg-target.h | 3 --- tcg/mips/tcg-target.h | 3 --- tcg/ppc/tcg-target.h | 2 -- tcg/ppc64/tcg-target.h | 1 - tcg/s390/tcg-target.h | 2 -- tcg/sparc/tcg-target.h | 2 -- tcg/tcg.c | 4 ---- tcg/tci/tcg-target.h | 3 --- 12 files changed, 2 insertions(+), 55 deletions(-) -- 1.7.9.5
