Question about toolchain and objdump's output on ia64/mips/mipsel

Hello, while working on http://wiki.debian.org/Projects/ImprovedDpkgShlibdeps I'm discovering some arch-specific differences in the objdump -T output of libraries. * On ia64, static functions appear in objdump's output and they are marked as local. See my previous message to debian-ia64:

Re: Question about toolchain and objdump's output on ia64/mips/mipsel

Raphael Hertzog wrote: Hello, while working on http://wiki.debian.org/Projects/ImprovedDpkgShlibdeps I'm discovering some arch-specific differences in the objdump -T output of libraries. * On ia64, static functions appear in objdump's output and they are marked as local. See my

Re: Question about toolchain and objdump's output on ia64/mips/mipsel

On Tue, Aug 14, 2007 at 02:03:16PM +0100, Thiemo Seufer wrote: I presume this applies only to static functions whose address wasn't taken inside the module. Otherwise this would be a bug for e.g. callbacks exported via a function pointer. I mentioned it in my reply to Raphael [1] but I think