From: "David S. Miller" <davem@redhat.com>
To: panto@intracom.gr
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Standard way of generating assembler offsets
Date: Mon, 08 Oct 2001 02:49:46 -0700 (PDT) [thread overview]
Message-ID: <20011008.024946.74749362.davem@redhat.com> (raw)
In-Reply-To: <3BC1735F.41CBF5C1@intracom.gr>
In-Reply-To: <28136.1002196028@ocs3.intra.ocs.com.au> <3BC1735F.41CBF5C1@intracom.gr>
From: Pantelis Antoniou <panto@intracom.gr>
Date: Mon, 08 Oct 2001 12:35:27 +0300
If anyone is interested I have already made a perl
script that produces assembler offsets from structure
members.
It doesn't need to run native since it reads the
header files, extract the structures and by using
objdump calculates the offsets automatically.
BTW, I assume you have already taken a look at how we
do this on Sparc64. See arch/sparc64/kernel/check_asm.sh
and the "check_asm" target in arch/sparc64/kernel/Makefile
It also works in all cross-compilation etc. environments.
And I bet it would work on every platform with very minimal
changes, if any.
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-10-08 9:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 11:47 [RFC] Standard way of generating assembler offsets Keith Owens
2001-10-04 15:36 ` george anzinger
2001-10-05 5:48 ` Keith Owens
2001-10-06 5:21 ` Keith Owens
2001-10-08 9:35 ` Pantelis Antoniou
2001-10-08 17:29 ` george anzinger
2001-10-08 17:56 ` Georg Nikodym
2001-10-08 19:00 ` george anzinger
2001-10-09 7:38 ` Pantelis Antoniou
2001-10-09 9:28 ` David S. Miller
2001-10-08 9:49 ` David S. Miller [this message]
2001-10-09 7:25 ` Pantelis Antoniou
2001-10-09 9:24 ` David S. Miller
2001-10-14 11:27 ` Keith Owens
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=20011008.024946.74749362.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=panto@intracom.gr \
/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;
as well as URLs for NNTP newsgroup(s).