Re: Host/Target confusion in Dwarf output

[Eric Botcazou <ebotcazou at libertysurf dot fr>]

> They don't REQUIRE it, but just miss a lot of optimization if that isn't
> the case (since things that would otherwise be CONST_INT will now be
> CONST_DOUBLE and folding will be harder).

#  need_64bit_hwint	Set to yes if HOST_WIDE_INT must be 64 bits wide
#			for this target.  This is true iff this target
#			supports "long" or "wchar_t" wider than 32 bits.

alpha*-*-*)
	cpu_type=alpha
	need_64bit_hwint=yes
	;;

x86_64-*-*)
	cpu_type=i386
	extra_headers="mmintrin.h mm3dnow.h xmmintrin.h emmintrin.h
		       pmmintrin.h tmmintrin.h ammintrin.h smmintrin.h
		       nmmintrin.h"
	need_64bit_hwint=yes
	;;

ia64-*-*)
	extra_headers=ia64intrin.h
	need_64bit_hwint=yes
	;;

mips*-*-*)
	cpu_type=mips
	need_64bit_hwint=yes
	;;

powerpc*-*-*)
	cpu_type=rs6000
	extra_headers="ppc-asm.h altivec.h spe.h"
	need_64bit_hwint=yes
	case x$with_cpu in
	    xpowerpc64|xdefault64|x6[23]0|x970|xG5|xpower[3456]|xpower6x|xrs64a)
		cpu_is_64bit=yes
		;;
	esac
	;;
rs6000*-*-*)
	need_64bit_hwint=yes
	;;

sparc64*-*-*)
	cpu_type=sparc
	need_64bit_hwint=yes
	;;

spu*-*-*)
	cpu_type=spu
	need_64bit_hwint=yes
	;;

s390*-*-*)
	cpu_type=s390
	need_64bit_hwint=yes
	;;

sh[123456789lbe]*-*-*)
	cpu_type=sh
	need_64bit_hwint=yes
	;;

-- 
Eric Botcazou