public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Offsets from C struct into assembler
Date: Tue, 29 Jan 2002 09:36:44 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805949@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805940@msgid-missing>

David Mosberger <davidm@hpl.hp.com> writes:

|> >>>>> On Tue, 29 Jan 2002 08:06:46 +0100, Christian Hildner <christian.hildner@hob.de> said:
|> 
|>   Christian> Although it would be a nice feature of the gcc if it
|>   Christian> could include C headers combined with an assembler
|>   Christian> directive for using the offsets the simple solution with
|>   Christian> print_offsets does it's job fine. The good thing here is
|>   Christian> that awk isn't needed.
|> 
|> It's not difficult to fix print_offsets.c to avoid awk.  We could use
|> directives of the form:
|> 
|>   asm volatile ("uc_rnat = %0"::"i"(offsetof (struct _Unwind_Context, rnat)));
|> 
|> for this purpose (this is a cut & paste from gcc's unwind-ia64.c).

You still have to post-process the output to make it usefull for the
assembler.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


      parent reply	other threads:[~2002-01-29  9:36 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
2002-01-29  8:39 ` David Mosberger
2002-01-29  9:36 ` Andreas Schwab [this message]

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-105590698805949@msgid-missing \
    --to=schwab@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox