This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gnat cross-compiles ?
- From: root <joel at OARcorp dot com>
- To: Joe Buck <Joe dot Buck at synopsys dot com>
- Cc: Andreas Schwab <schwab at suse dot de>, espie at nerim dot net, gcc at gcc dot gnu dot org
- Date: Thu, 06 Jun 2002 12:59:12 -0500
- Subject: Re: gnat cross-compiles ?
- Organization: OAR Corporation
- References: <200206061537.IAA18203@atrus.synopsys.com>
- Reply-to: joel dot sherrill at OARcorp dot com
Joe Buck wrote:
>
> Marc Espie <espie@nerim.net> writes:
> >
> > |> I'd like to know which processors are happy with gnat in 3.1 (or the 3.1
> > |> branch), and whether cross-compiles have a chance to work, before I embark
> > |> on a wild goose chase...
>
> Andreas Schwab writes:
> > We have already built gnat for ia64, alpha and ppc, via cross compiling
> > from i386. Sparc, s390 and x86-64 are on my todo list.
>
> I think that cross-compiling is the most confusing part of GCC, we
> certainly get more questions about that than anything else, even from
> experts. Andreas, would you be willing to write a note describing your
> process? It doesn't need to be thorough, it could be as simple as just
> listing the exact sequence of commands you used to produce, say, the ppc
> compiler by cross-compilation from i386.
I tried to build crosses for all of the RTEMS targets. Here
is a post of my results.
http://gcc.gnu.org/ml/gcc/2002-05/msg00155.html
Summary: I get good results for sparc-rtems on ACATS. I can build
a number of others. Some have CPU specific failures (mips). Other
CPUs do not have the exception processing support and fail in raise.c.
I would really like to know what is required to be supported to
get by raise.c. This is required to fix at least the i960, m68k and sh.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985