This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Peter Barada wrote: > > >What would it take to add a comparable 68060 multilib? > > These two changes: > > -MULTILIB_OPTIONS = m68000/m68020/m5200/mcpu32 m68881/msoft-float > +MULTILIB_OPTIONS = m68000/m68020/m5200/mcpu32/m68040/68060 m68881/msoft-float > > > -MULTILIB_MATCHES = m68000=mc68000 m68000=m68302 mcpu32=m68332 m68020=mc68020 m68020=m68040 > +MULTILIB_MATCHES = m68000=mc68000 m68000=m68302 mcpu32=m68332 m68020=mc68020 > > Of course it assumes that the code thats in the libgcc files is > optimizable for the 68040... It it easy to forget the libgcc is not the only thing that is multilib'ed. newlib is also multilib'ed. I assume the C++ libraries are as well. To me, this is the reason you want more precise multilibs -- especially in embedded environments where cycles count and the complexity of emulating instructions is unwarranted. And FWIW RTEMS is in the process of being reorganized to be multilib'ed as well. So now you even have the RTOS following that path. > ------ > Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ > Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com -- 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 ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |