This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: V3 and cross-compiler (AIX 4.3 64-bit mode)
- To: David Edelsohn <dje at watson dot ibm dot com>
- Subject: Re: V3 and cross-compiler (AIX 4.3 64-bit mode)
- From: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
- Date: Fri, 8 Jun 2001 23:29:20 +0200 (MEST)
- Cc: rboehne at ricardo-us dot com, Mark Mitchell <mark at codesourcery dot com>, bkoz at redhat dot com, pedwards at disaster dot jaj dot com, libstdc++ at gcc dot gnu dot org, Alexandre Oliva <aoliva at redhat dot com>, gcc-patches at gcc dot gnu dot org
- References: <ro@TechFak.Uni-Bielefeld.DE><15137.14101.172768.270702@xayide.TechFak.Uni-Bielefeld.DE><200106082124.RAA23496@makai.watson.ibm.com>
David Edelsohn writes:
> >>>>> Rainer Orth writes:
>
> Rainer> Why leave this to the user to specify? Have a look at the mips*-*-*
> Rainer> (mabi=64) and sparc*-*-* (m64) cases, adding a test that the resulting
> Rainer> binary really executes. It's both simpler for the user and more reliable.
>
> Because unlike Irix and Sparc, one actually can and should be able
> to build 64-bit AIX multilib on a 32-bit system. If it were not for
That's true for those systems as well: you can install a 64-bit development
environment on both IRIX and Solaris on 32-bit-only systems and compile for
64-bit, provided you don't try to execute the resulting binary.
> self-querying the limits, this would work. If the user substitutes a
> correct std_limits.h, it will work.
Still your approach is more work for the casual user. I'd suggest doing it
the other way round: enable 64-bit if you can build and execute a 64-bit
binary, and if this test fails, allow the user to override this if he knows
what he's doing.
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
Email: ro@TechFak.Uni-Bielefeld.DE