Matthias, we changed the toolchain defaults after this bug had been witnessed.
Also I change oo.o to use -mfloat-abi=soft since I thought uno2cpp.cxx needed porting in case softfp used fpu regs to pass args in some cases (e.g. function calls within the same binary). On second thought this doesn't make any sense since that means functions would have to be modified during link. Calaon confirmed that softfp never used fpu regs to pass args. So it seems uno2cpp.cxx should be changed to allow softpfp and reject -mfloat-abi=hard which is hard to test for. But this is unrelated to our oo.o startup issue sadly.
Matthias, we changed the toolchain defaults after this bug had been witnessed.
Also I change oo.o to use -mfloat-abi=soft since I thought uno2cpp.cxx needed porting in case softfp used fpu regs to pass args in some cases (e.g. function calls within the same binary). On second thought this doesn't make any sense since that means functions would have to be modified during link. Calaon confirmed that softfp never used fpu regs to pass args. So it seems uno2cpp.cxx should be changed to allow softpfp and reject -mfloat-abi=hard which is hard to test for. But this is unrelated to our oo.o startup issue sadly.