configure: unify x86_64 and x32
The only difference between the two, as far as either configure or Meson are concerned, is in the multilib flags passed to the compiler. For QEMU, this fixes the handling of TYPE_OLDDEVT in include/exec/user/thunk.h and enables testing of dirty ring buffer, because both are using HOST_X86_64. For tests/tcg, this means that on a hypothetical x32 host the cross compiler will not be used to build the tests. Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
parent
d8ff892dc2
commit
4da270be1c
6
configure
vendored
6
configure
vendored
@ -647,6 +647,7 @@ case "$cpu" in
|
||||
cpu="i386"
|
||||
CPU_CFLAGS="-m32" ;;
|
||||
x32)
|
||||
cpu="x86_64"
|
||||
CPU_CFLAGS="-mx32" ;;
|
||||
x86_64|amd64)
|
||||
cpu="x86_64"
|
||||
@ -3719,7 +3720,7 @@ fi
|
||||
if test "$linux" = "yes" ; then
|
||||
mkdir -p linux-headers
|
||||
case "$cpu" in
|
||||
i386|x86_64|x32)
|
||||
i386|x86_64)
|
||||
linux_arch=x86
|
||||
;;
|
||||
ppc|ppc64)
|
||||
@ -3901,9 +3902,6 @@ if test "$skip_meson" = no; then
|
||||
i386)
|
||||
echo "cpu_family = 'x86'" >> $cross
|
||||
;;
|
||||
x86_64|x32)
|
||||
echo "cpu_family = 'x86_64'" >> $cross
|
||||
;;
|
||||
*)
|
||||
echo "cpu_family = '$ARCH'" >> $cross
|
||||
;;
|
||||
|
@ -355,7 +355,7 @@ if not get_option('tcg').disabled()
|
||||
tcg_arch = 'tci'
|
||||
elif config_host['ARCH'] == 'sparc64'
|
||||
tcg_arch = 'sparc'
|
||||
elif config_host['ARCH'] in ['x86_64', 'x32']
|
||||
elif config_host['ARCH'] == 'x86_64'
|
||||
tcg_arch = 'i386'
|
||||
elif config_host['ARCH'] == 'ppc64'
|
||||
tcg_arch = 'ppc'
|
||||
@ -1806,7 +1806,6 @@ disassemblers = {
|
||||
'hppa' : ['CONFIG_HPPA_DIS'],
|
||||
'i386' : ['CONFIG_I386_DIS'],
|
||||
'x86_64' : ['CONFIG_I386_DIS'],
|
||||
'x32' : ['CONFIG_I386_DIS'],
|
||||
'm68k' : ['CONFIG_M68K_DIS'],
|
||||
'microblaze' : ['CONFIG_MICROBLAZE_DIS'],
|
||||
'mips' : ['CONFIG_MIPS_DIS'],
|
||||
|
Loading…
Reference in New Issue
Block a user