From: law@redhat.com
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: is casting of function descriptor assignments for ia64 ONLY a
Date: Thu, 03 Jan 2002 17:11:20 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805736@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805734@msgid-missing>
> Not just ia64, powerpc 64 as well. You are assuming that all pointers
> are the same format when that is not guaranteed by the C standard. On
> most architectures they are the same, you can convert a function
> pointer to a void pointer and back again but it is not defined
> behaviour.
>
> On IA64 and PPC64 the function pointer does not reference the function
> itself, instead it points to a function descriptor. The function
> descriptor contains a pointer to the function code plus additional data
> such as a pointer to the global data to be used when the function is
> called. This is mandated by the architecture software ABI.
Also true for HPPA targets.
jeff
next prev parent reply other threads:[~2002-01-03 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 8:35 [Linux-ia64] Re: is casting of function descriptor assignments for ia64 ONLY a good idea? Keith Owens
2002-01-03 17:11 ` law [this message]
2002-01-03 17:35 ` Grant Grundler
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-105590698805736@msgid-missing \
--to=law@redhat.com \
--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