On Mon, 31 Mar 2008, Hasjim Williams wrote: > If someone can get iwmmxt support working in everything, then we might > be able to do the same for MaverickCrunch, since it is very similar work > to get one ARM coprocessor working as it is to get another working. > Half of the support for the iWMMXt processor has already been written > and there is proper documentation. Currently iwmmxt is only enabled in > certain applications in openembedded (rather than system-wide) because > of this reason. I am not sure if it is only exception unwinding that > isn't working on iWMMXt, or if there is something else that also needs > to be written.
iWMMXt unwind support has been in GCC since my patch <http://gcc.gnu.org/ml/gcc-patches/2007-01/msg00049.html>. That illustrates the sort of thing that needs changing to implement unwind support for a new coprocessor. Obviously you need to get the unwind specification in the official ARM EABI documents first before implementing it in GCC, and binutils will also need to support generating correct information given .save directives for the coprocessor registers. For setjmp/longjmp support in glibc you also need to get an HWCAP value allocated in the kernel. -- Joseph S. Myers [EMAIL PROTECTED]
