This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
On Tue, 2 Sep 1997, Robert J. Brown wrote: > Gunter> Let me also point you to the work of Eric Norum at > Gunter> Univ. Sasketchuan (sp?), Canada, who built another Linux > Gunter> GDB/BDM system. His system has already 68360 > Gunter> support. Sorry, no precise link at hand. > > Gunter> Greetings gm -- Gunter Magin magin[AT]skil.camelot.de > > I am currently working on a 68360 project and would like very much to > get us off of a proprietary compiler, primarily so that the Pentium, > Sparc, 68340, 68360, and PPC cpus would all use the same compiler > front end and libraries. It would be nice to switch to RTEMS someday > also, but first I want to do the compiler. The 68360 is a very well supported CPU for RTEMS. Eric Norum did the BSP, a port of the KA9Q TCP/IP stack, and a boat load of other stuff. He deservices a nice plug for all of his work. :) The tool chain support for RTEMS is moving up. binutils 2.8.1 included fully working RTEMS support. gcc 2.8 should include RTEMS support and egcs snapshots already include it. newlib 1.8.0 almost has working RTEMS support so the next release should be fine. With egcs, it looks like the C++ libraries will be working for RTEMS. This means there are CPU-rtems tool chain configurations which can be built one-tree style. Right now, the CPU can be m68k, powerpc, i386, i386-go32, i960, hppa1.1, mips64, sparc, and (with any luck coming soon) sh. What needs to be addressed most now is gdb support. If anyone is willing and able to work on rtems gdb support, please let me know. Thanks. --joel Joel Sherrill Director of Research & Development joel@OARcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (205) 722-9985