On Sun, Jun 10, 2012 at 08:03:24PM +0200, Thomas Preud'homme wrote: > Le dimanche 10 juin 2012 20:01:11, Michael Matz a écrit : > > > but we don't build a libtcc1 for ARM > > > > ... I think we should do so then. As it seems the various arithmetic > > routines of libtcc1.c aren't needed on arm it would only contain alloca. > > I'd vote for the assembler implementation (don't know if it would have to > > differ between the eabi and oldabi variants). > > It doesn't use VFP so it will work for both ABI. It also work for the new > eabihf which I introduced as there is no float parameter.
Compiler generated calls have been chosen to allow the use of libgcc_s.so.1 on ARM EABI and OABI. It is needed for divisions, 64-bit shifts, and some floating point conversion. One day we might also support devices without floating point hardware/emulator, where we could use the EABI soft float functions already contained in libgcc. I also added a configure option --with-libgcc to make TinyCC automatically link to libgcc_s.so.1 instead of libtcc1.a. If we now start to supply a libtcc1.a that does not include the functions from libgcc_s.so.1, we need to link to two libraries. Daniel _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
