Le lundi 17 octobre 2011 22:41:32, vous avez écrit : > Package: tcc > Version: 0.9.26~git20110616.330d2ee-4 > Severity: wishlist > > Hi Hi, > > It would be nice if TCC supported the hard-float ABI used on armhf > (uses the FPU regs to pass floating point values). My question might be stupid but are you talking about the code tcc generate or the code in which tcc is compiled? I guess you're talking about the code in which tcc itself is compiled since tcc has only one ABI for generated code as far as I know. > > In fact, it would be nice if TCC allowed selection of the ARM ABI it's > targetting, e.g. ARMv4...ARMv7, Thumb/ARM mode, OABI vs. EABI, soft VFP > / hard VFP / no VFP. > > (Note that currently the supported ABI is the one of the buildd, which > might be higher than the base requirement to run the Debian port.) I guess you are refering to the line NATIVE_DEFINES+=$(if $(shell grep -l "^Features.* \(vfp\|iwmmxt\) " /proc/cpuinfo),-DTCC_ARM_VFP) in Makefile. Did I miss some other line?
I would happily work on it as I'm myself using armhf since recently but I don't know enough about the different ARM ABI so could you suggest me a list of ABI and the feature I should put inside (or point me to a documentation for this second part)? By the way, should I wait for this bug to be solved before adding armhf to the list of supported architecture as requested by you in bug #645673 or directly upload with armhf enabled and work in a second time on this issue? > > Thanks! Thanks for your work on armhf. Best regards, Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
