This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: m68k problem and libstdc++
- From: Richard Henderson <rth at redhat dot com>
- To: Craig Rodrigues <rodrigc at mediaone dot net>
- Cc: libstdc++ at gcc dot gnu dot org, gcc at gcc dot gnu dot org, schwab at suse dot de
- Date: Thu, 3 Jan 2002 17:52:32 -0800
- Subject: Re: m68k problem and libstdc++
- References: <20020103195503.A12936@mediaone.net>
On Thu, Jan 03, 2002 at 07:55:03PM -0500, Craig Rodrigues wrote:
> I'm not a 68000 asm expert. Does anyone have an idea as
> to what the fix could be?
Some preprocessor hackery and or configure hackery.
Virtually all real operating systems don't support anything less
than 68020, because that's the first one that had a built-in mmu.
There are some very antiquated exceptions which are notable only
in the amazing jumped through to bolt an mmu on the side.
So we have to identify which m68k targets are for embedded
operating systems and which might possibly run on a true 68000.
We then have to see what preprocessor macros are defined, to see
if we can distinguish between 68000 and 68020. This will be very
nasty because there's little or no uniformity here.
Alternately, we force those targets to use config/cpu/generic.
Alternately, we list those targets that cannot run on 68000 and
don't make m68k-*-* do anything.
Probably the last is easiest.
r~