Comment 3 for bug 889985

The context for this is evaluation of an initial 'prebuilt Linaro toolchain' drop from Michael Hope. My debugger is ARM's DS-5 rather than GDB - so far as I know it only uses the first method that you mention.

I can't tell you exactly how it was built, but it came from http://people.linaro.org/~michaelh/incoming/gcc-linaro-arm-linux-gnueabi-4.6-2011.09-1.tar.bz2 and arm-linux-gnueabi-gcc --version says 'arm-linux-gnueabi-gcc (Linaro 2011.09+bin1) 4.6.2 20110908 (prerelease)'.

The ABI document I am looking at is 'DWARF for the ARM Architecture' which can be found at http://infocenter.arm.com/help/index.jsp under 'ARM software development tools->Application Binary Interface->DWARF for the ARM Architecture' - a direct link that might work is http://infocenter.arm.com/help/topic/com.arm.doc.ihi0040a/IHI0040A_aadwarf.pdf. The relevant section does say 'obligations on producers of relocatable files' - I'm seeking confirmation of exactly what is meant by that in this case.

The target system that I'm running on is a years old filesystem built within ARM, but __addsf3 was statically linked in my test case so I think that the target system is not relevant in this case and anyway not so relevant for you as I'm not using GDB. Feel free to correct me.

As with bug 889984, this might be an issue for the folks building the prebuilt toolchain deliverable rather than the gcc maintainers.