public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kaz Kylheku <kkylheku@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Easier way to generate stuff like asm-offsets.
Date: Fri, 20 Nov 2009 16:56:14 -0800	[thread overview]
Message-ID: <3f43f78b0911201656o6d222e6fkf5ef8533c8ee6e16@mail.gmail.com> (raw)

Hey all,

You can use declarations and the ``nm'' utility to discover sizes of
types, structure offsets and stuff like that.

There is no need to grep material from the assembly code itself.

I'm looking into this as a technique for to use in ./configure scripts
when a program is being cross-compiled.

Then I remembered that the Linux kernel does something to pull out
structure member offsets
for use in assembly code. How are they doing that, I wondered? I took
a look and saw that it
was done with a complicated hack.

Here is the simple trick:

  /* file test.c */

  #include <stddef.h>  /* for offsetof macro */

  struct foo { char padding[43]; int member; };

  char offsetof_foo_member[offsetof(struct foo, member)];

Now we compile test.c:

$ /path/to/toolchain/bin/arch-prefix-gcc test.c -c

Then we can use the ``nm'' tool (the toolchain should have binutils in it):

$ /path/to/toolchain/bin/arch-prefix-nm -t d -P foo.c   # decimal
output, posix format
offsetof_foo_member C 00000044 00000044

There we go, 44 bytes.  Simple.  This is almost an #include file;
we just have to do some simple filtering, such as:

$ /path/to/toolchain/bin/arch-prefix-nm -t d -P test.o | awk '{ print
"#define", $1, $4 }'
#define offsetof_foo_member 00000044

:)

Cheers ...

             reply	other threads:[~2009-11-21  0:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-21  0:56 Kaz Kylheku [this message]
2009-11-21  4:43 ` Easier way to generate stuff like asm-offsets Ben Pfaff
2009-11-21  6:10 ` Michal Jaegermann

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=3f43f78b0911201656o6d222e6fkf5ef8533c8ee6e16@mail.gmail.com \
    --to=kkylheku@gmail.com \
    --cc=linux-kernel@vger.kernel.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