This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC build failed with your patch on 2001-01-09T11:35:00Z.
- To: Richard Henderson <rth at redhat dot com>
- Subject: Re: GCC build failed with your patch on 2001-01-09T11:35:00Z.
- From: Jakub Jelinek <jakub at redhat dot com>
- Date: Tue, 9 Jan 2001 23:12:46 +0100
- Cc: David Edelsohn <dje at watson dot ibm dot com>, Mark Mitchell <mark at codesourcery dot com>, aoliva at redhat dot com, geoffk at redhat dot com, gcc at gcc dot gnu dot org, gcc-regression at gcc dot gnu dot org, grahams at redhat dot com, jsm28 at cam dot ac dot uk, mhayes at redhat dot com, neil at daikokuya dot demon dot co dot uk, osk at hem dot passagen dot se
- References: <mark@codesourcery.com> <200101092050.PAA38976@mal-ach.watson.ibm.com> <20010109135807.A4380@redhat.com>
- Reply-To: Jakub Jelinek <jakub at redhat dot com>
On Tue, Jan 09, 2001 at 01:58:07PM -0800, Richard Henderson wrote:
> > Because some targets are runtime selectable between 32-bits and
> > 64-bits, this is not limited to targets of a particular width or
> > cross-compilers. Targetting a different width is a subset of a
> > cross-compiler. The hwint.h decision depends upon MAX_LONG_TYPE_SIZE
> > which is the maximum of the runtime selectable values.
>
> The class of targets for which I consider the patch to be incorrect
> are 32-bit natives for which there is a runtime selectable 64-bit
> variant -- PA, MIPS, and PowerPC. Sparc is in a different class
> since it controls the presence of Sparc64 code with SPARC_BI_ARCH,
> which is not defined by default for 32-bit natives.
>
> For other 64-bit targets I do not consider the patch broken, as
> otherwise the cross-compile won't work.
Once Sparc64 will be more common, SPARC_BI_ARCH will be the default in every
compiler, so Sparc will fall into the same category as PA, MIPS and PPC.
What we currently do in the gcc-2.96RH compiler on sparc is a little bit
hackish:
the compiler is either native 64bit -> 32bit/64bit or
native 32bit with HOST_WIDE_INT long long (forced in xm.h) -> 32bit/64bit
(and in the latter case with alternate C and C++ compilers
native 32bit with HOST_WIDE_INT long -> 32bit which get selected by adding
an additional -B prefix in the driver if doing 32bit compilation. So the
user can choose whether he wants to have faster compilations or save some
space and only use the long long compiler).
Jakub