This is the mail archive of the
mailing list for the GCC project.
Re: -m32 only ia32 compiler?
- To: Jakub Jelinek <jakub at redhat dot com>
- Subject: Re: -m32 only ia32 compiler?
- From: Andreas Jaeger <aj at suse dot de>
- Date: 04 May 2001 08:46:32 +0200
- Cc: rth at redhat dot com, aoliva at redhat dot com, jh at suse dot cz, gcc at gcc dot gnu dot org
- References: <20010503194906.I1863@sunsite.ms.mff.cuni.cz>
Jakub Jelinek <firstname.lastname@example.org> writes:
> With the recent 32->64bit cross patch suddenly HOST_WIDE_INT is long long on
> ia32 native, eventhough 99.999% people don't need -m64 support on ia32.
> Shouldn't there be separate configuration for i386-*-* (which would create a
> -m32 only compiler) and x86_64-*-* (which would create a -m32/-m64
> compiler)? On the SPARC, the compiler can be configured both to support only
> -m32 and -m32/-m64 (and actually in the distribution we use a driver hack,
> so that for -m32 compilations it looks into a special -B path where it finds a
> -m32 only cc1/cc1plus).
Do you suggest to use a construct similar to SPARC_BI_ARCH for i386?
SuSE Labs email@example.com