All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Offsets from C struct into assembler
Date: Tue, 29 Jan 2002 07:06:46 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805947@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805940@msgid-missing>

David Mosberger schrieb:

> >>>>> On Tue, 29 Jan 2002 07:59:43 +1100, Keith Owens <kaos@ocs.com.au> said:
>
>   Keith> On Mon, 28 Jan 2002 08:11:23 -0700, n0ano@indstorage.com
>   Keith> wrote:
>   >> Or you can check out how the IA64 Linux kernel does this.  The
>   >> file `arch/ia64/tools/printoffsets.c' is a program that is
>   >> compiled and, when run, generates the file `include
>   >> asm-ia64/offsets.h' which is an ASM include file containing
>   >> structure offsets.
>
>   Keith> That tool is disappearing in 2.5 kernels.  All architectures
>   Keith> will use the same method for generating asm offsets, the one
>   Keith> I included in my previous mail.
>
> As of v2.5.3-pre5 I don't see any sign of your new kernel build
> environment being part of Linus' tree.  Perhaps it will be accepted
> some day, but until that happens, the scheme described by Don is the
> correct one.
>
>         --david

Although it would be a nice feature of the gcc if it could include C headers
combined with an assembler directive for using the offsets the simple solution
with print_offsets does it's job fine. The good thing here is that awk isn't
needed.

Thanks,

Christian



  parent reply	other threads:[~2002-01-29  7:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28  8:56 [Linux-ia64] Offsets from C struct into assembler Christian Hildner
2002-01-28 12:16 ` Keith Owens
2002-01-28 15:11 ` n0ano
2002-01-28 20:59 ` Keith Owens
2002-01-28 21:15 ` David Mosberger
2002-01-29  7:06 ` Christian Hildner [this message]
2002-01-29  8:39 ` David Mosberger
2002-01-29  9:36 ` Andreas Schwab

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=marc-linux-ia64-105590698805947@msgid-missing \
    --to=christian.hildner@hob.de \
    --cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.