From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sources.redhat.com
Subject: Re: [commit] new observer.[hc] files
Date: Fri, 28 Feb 2003 16:10:00 -0000 [thread overview]
Message-ID: <jeu1eowfmk.fsf@sykes.suse.de> (raw)
In-Reply-To: <20030228152256.GB23109@nevyn.them.org> (Daniel Jacobowitz's message of "Fri, 28 Feb 2003 10:22:56 -0500")
Daniel Jacobowitz <drow@mvista.com> writes:
|> Is this extra indirection really necessary? Because I'm 99% sure it
|> won't work on several 64-bit platforms. Function pointers and data
|> pointers are not required to have the same size; on IA-64 I believe
|> that a function pointer is 128 bits and a data pointer is 64 bits.
Function pointer are still 64 bits on ia64 (and ppc64). They do not point
to the code itself, but to a descriptor which contains the actual code
pointer and the gp value. But I agree that mixing function pointer and
object pointers should be avoided.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, 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."
next prev parent reply other threads:[~2003-02-28 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 7:38 Joel Brobecker
2003-02-28 15:22 ` Daniel Jacobowitz
2003-02-28 16:10 ` Andreas Schwab [this message]
2003-02-28 16:14 ` Andrew Cagney
2003-02-28 16:39 ` Daniel Jacobowitz
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=jeu1eowfmk.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sources.redhat.com \
/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