From: Martin Kittel <debian@martin-kittel.de>
To: gcc-help@gcc.gnu.org
Subject: Gcc-4.0 vtable layout on IA64
Date: Mon, 18 Jul 2005 17:36:00 -0000 [thread overview]
Message-ID: <42DBE87D.9080600@martin-kittel.de> (raw)
Hi,
While trying to get the MaxDB sources compiled with gcc 4.0 on an IA64
machine I stumbled over the following comment describing the vtable layout:
* gcc 3.1 on ia64 uses new c++ abi (without runtime type info):
*
* pInterface -> 0 ----------- 0 -----------------------
* ! virt.Meth ! ------->| gp0 | Method 0 |
* ----------- |------------| |
* ! : ! 8 | offset0 | |
* ------------+----------|
* 16 | gp1 | Method 1 |
* ------------| |
* 24 | offset1 | |
* ------------+----------|
* | : | : |
* :
* | : | : |
* ------------+----------|
* 16*(n-1)+0 | gp n | Method n |
* ------------| |
* 16*(n-1)+8 | offset n | |
* ------------+----------
I was wondering if this is still correct with gcc 4.0 or whether there
the formula should be 8*(n-1) to access method n (as that seems to
correspond to what you have on i386)?
Thanks for any help,
Martin.
reply other threads:[~2005-07-18 17:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42DBE87D.9080600@martin-kittel.de \
--to=debian@martin-kittel.de \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).