From: george anzinger <george@mvista.com>
To: Pantelis Antoniou <panto@intracom.gr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Standard way of generating assembler offsets
Date: Mon, 08 Oct 2001 10:29:56 -0700 [thread overview]
Message-ID: <3BC1E294.1A4FB12D@mvista.com> (raw)
In-Reply-To: <28136.1002196028@ocs3.intra.ocs.com.au> <3BC1735F.41CBF5C1@intracom.gr>
Pantelis Antoniou wrote:
>
> Hi there.
>
> 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.
>
> Maybe it needs some more work for what you describe,
> but it's exactly what you describe.
>
> If you're interested please email me directly for
> more information.
>
One of the problems with this sort of thing is that it has a hard time
getting the CPP macros right. The best way to do this sort of thing is
to actually compile the header file with all the CONFIG defines and a
set of tools (read macros) that produce the required offsets. This way
you get what you want and don't have to reinvent the CPP stuff. It also
allows production of #define constants and other constructs that folks
push into CPP, in a very simple and straight forward manner.
Been there, done that.
George
next prev parent reply other threads:[~2001-10-08 17:37 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 9:49 ` David S. Miller
2001-10-09 7:25 ` Pantelis Antoniou
2001-10-09 9:24 ` David S. Miller
2001-10-14 11:27 ` Keith Owens
2001-10-08 17:29 ` george anzinger [this message]
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
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=3BC1E294.1A4FB12D@mvista.com \
--to=george@mvista.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