On Mon, Jul 12, 2010, Dave Martin wrote:
- Use ABI tagging (high effort, involving modifications to affected
projects - permits hardvfp ABI for explicitly selected functions)
This is the first time I hear this suggested, and it's quite a nice option
I don't understand how much effort it implies, nor what kind of adverse side effects in might have: size of binaries, compilation time perhaps?
Is the idea to select some functions to be built for each ABI, or rather build a while piece of software (with some toolchain flags) turning on the generation of the two ABIs with relevant tags on all functions taking floats as arguments? Will the toolchain be involved in taking the decision of which functions to provide for the two ABIs?