Hi - > >which means that libmudflap needs to be ported to sh-elf. > > How should I start the porting? Do you have any document related to such > porting? [...]
First thing is to get past that autoconf error. Check your linker script for the default entry point symbol's name, and give it to libmudflap/configure.ac (then regenerate configure). Next, overcome build problems (if any) to the extent that a libmudflap.a gets compiled. Then, start running the test suite. It does not cover all the libc function wrappers, so at this point you might as well start compiling your own smaller code with -fmudflap and see what happens. It may be reassuring that it is not sh-elf per se that needs porting, but rather your runtime C library. There is little to no architecture-specific code in there. - FChE
