From: "Alexander Sirotkin" <demiourgos@gmail.com>
To: "Ralf Baechle" <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: 0 function size
Date: Mon, 5 Mar 2007 18:28:42 +0200 [thread overview]
Message-ID: <c4357ccd0703050828g7ee6eb30w516bb0d60928bbc6@mail.gmail.com> (raw)
In-Reply-To: <20070305162028.GA786@linux-mips.org>
On 3/5/07, Ralf Baechle <ralf@linux-mips.org> wrote:
> On Mon, Mar 05, 2007 at 04:19:18PM +0200, Alexander Sirotkin wrote:
>
> > I'm trying to see the function sizes for some object file compiled for
> > MIPS. On x86 one can use objdump or readelf to see the sizes, however
> > for same weird reason on MIPS these routines show 0 for all functions.
> >
> > Any idea what I'm missing ?
>
> Works fine here:
>
> 801f3f10 l F .text 00000074 rekey_seq_generator
> 80327f2c l O .data 00000028 rekey_work
> 80345dd0 l F .init.text 00000020 seqgen_init
> 801f3fd0 l F .text 000000f4 uuid_strategy
> 801f40c4 l F .text 0000012c proc_do_uuid
> 801f42e0 l F .text 0000012c extract_entropy_user
> 801f440c l F .text 0000000c urandom_read
> 801f4418 l F .text 000000fc random_write
> 801f4514 l F .text 000001f4 random_ioctl
> 801f484c l F .text 00000090 random_poll
> 801f4ac8 l F .text 00000190 random_read
> 80327f64 l O .data 00000004 sysctl_poolsize
>
> So seems to be a defect with your particular toolchain or objdump or readelf.
Yeah, it is indeed a problem with the particular toolchain I was using. Thanks.
>
> Ralf
>
next prev parent reply other threads:[~2007-03-05 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 14:19 0 function size Alexander Sirotkin
2007-03-05 16:20 ` Ralf Baechle
2007-03-05 16:28 ` Alexander Sirotkin [this message]
2007-03-05 16:21 ` Rajat Jain
2007-03-05 16:27 ` Ralf Baechle
2007-03-06 11:06 ` Alexander Sirotkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4357ccd0703050828g7ee6eb30w516bb0d60928bbc6@mail.gmail.com \
--to=demiourgos@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox