From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [c++] Pointer to member overhaul
Date: Fri, 29 Dec 2006 19:06:00 -0000 [thread overview]
Message-ID: <m3hcveo72q.fsf@codesourcery.com> (raw)
In-Reply-To: <20061229025509.GA29152@nevyn.them.org> (Daniel Jacobowitz's message of "Thu, 28 Dec 2006 21:55:09 -0500")
This is great! I think TYPE_CODE_MEMBERPTR and TYPE_CODE_METHODPTR
are definitely the right approach; data members and member functions
are not merely a different kind of pointer target in the sense that,
say, functions are.
Since the change is so large, I just looked at the changes to the
cp-abi.h and gdbtypes.h interfaces, which I'm assuming pretty much
drive the rest of the stuff.
The comments in cp-abi.h refer to 'cplus_method_ptr_to_target', which
isn't defined anywhere.
The sentence "CONTENTS is the bytes forming the pointer to method"
isn't grammatical.
What is the use of TYPE_CODE_METHOD now? Is it equivalent to
TYPE_CODE_FUNC, except that it expects a 'this' pointer?
Is the representation of a pointer to a data member always simply an
offset from the start of the member pointer's class? It would be nice
if the comment for TYPE_CODE_MEMBERPTR said this; similarly, it would
be nice if the comment for TYPE_CODE_METHODPTR explained that the
representation varies from one ABI to the next, and one should use the
cp-abi.h methods to work with them. Say the word, and I'll write
these for you.
Why are vtable_function_descriptors and vbit_in_delta gdbarch methods
instead of cp-abi.h methods?
next prev parent reply other threads:[~2006-12-29 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 2:55 Daniel Jacobowitz
2006-12-29 19:06 ` Jim Blandy [this message]
2006-12-31 22:40 ` Daniel Jacobowitz
2006-12-31 22:55 ` Eli Zaretskii
2006-12-31 23:49 ` Daniel Jacobowitz
2007-01-03 18:15 ` Daniel Jacobowitz
2007-01-08 15:47 ` Ulrich Weigand
2007-01-08 15:52 ` Daniel Jacobowitz
2007-01-08 16:02 ` Ulrich Weigand
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=m3hcveo72q.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb-patches@sourceware.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