This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++ bootstrap failures on sparc-sun-solaris2.8 (analyzed)
- To: Richard Henderson <rth at redhat dot com>, Phil Edwards <pedwards at disaster dot jaj dot com>, Gabriel Dos Reis <gdr at codesourcery dot com>, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org, Alexandre Oliva <aoliva at redhat dot com>, Jan Hubicka <jh at suse dot cz>
- Subject: Re: libstdc++ bootstrap failures on sparc-sun-solaris2.8 (analyzed)
- From: David Edelsohn <dje at watson dot ibm dot com>
- Date: Tue, 31 Jul 2001 20:57:14 -0400
>>>>> Richard Henderson writes:
Richard> On Tue, Jul 31, 2001 at 08:21:33PM -0400, Phil Edwards wrote:
>> If `isainfo` doesn't include sparcv9, then we need to treat 64-bit
>> solaris like any other cross-compile; the hardware becomes irrelevent.
Richard> Err.. no. You've missed my point. Yes, one should have a
Richard> fallback strategy if you can't run 64-bit executables.
Richard> My point is that it's a waste of effort to check `isainfo`
Richard> or any other os-specific widgetry. Just run the program and
Richard> fall back if the execution fails.
Which is exactly what my patch from mid-June did:
http://gcc.gnu.org/ml/libstdc++/2001-06/msg00338.html
David