From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: METHOD_PTR_*?
Date: Wed, 17 Nov 2004 23:06:00 -0000 [thread overview]
Message-ID: <20041117225921.GA22472@nevyn.them.org> (raw)
In-Reply-To: <41996420.20607@gnu.org>
On Mon, Nov 15, 2004 at 09:21:20PM -0500, Andrew Cagney wrote:
> Daniel Jacobowitz wrote:
> >On Mon, Nov 15, 2004 at 08:13:00PM -0500, Andrew Cagney wrote:
> >
> >>Daniel Jacobowitz wrote:
> >>
> >>>On Tue, Nov 09, 2004 at 03:57:02PM -0500, Andrew Cagney wrote:
> >>>
> >>>
> >>>>Hello,
> >>>>
> >>>
> >>>>From value.h:
> >>>
> >>>>/* Pointer to member function. Depends on compiler implementation. */
> >>>>
> >>>>#define METHOD_PTR_IS_VIRTUAL(ADDR) ((ADDR) & 0x80000000)
> >>>>#define METHOD_PTR_FROM_VOFFSET(OFFSET) (0x80000000 + (OFFSET))
> >>>>#define METHOD_PTR_TO_VOFFSET(ADDR) (~0x80000000 & (ADDR))
> >>>>
> >>>>It also depends on the underlying architecture - not very 64-bit
> >>>>friendly :-/
> >>>
> >>>
> >>>Yuck!
> >>
> >>Can it for the moment be moved out of value.h?
> >
> >
> >What would that accomplish? Where would it move to?
>
> It would remove it from value.h.
That doesn't really answer my question... I assume that you want to
move it so that value.h only contains some set of "blessed" "struct
value" related routines. But this has no home obviously more
appropriate than its current home.
> cp-abi.h?
How about cp-support.h?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-11-17 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 21:54 METHOD_PTR_*? Andrew Cagney
2004-11-10 3:24 ` METHOD_PTR_*? Daniel Jacobowitz
2004-11-16 1:15 ` METHOD_PTR_*? Andrew Cagney
2004-11-16 1:24 ` METHOD_PTR_*? Daniel Jacobowitz
2004-11-16 4:56 ` METHOD_PTR_*? Andrew Cagney
2004-11-17 23:06 ` Daniel Jacobowitz [this message]
2005-02-09 0:45 ` METHOD_PTR_*? Andrew Cagney
2004-11-29 15:37 METHOD_PTR_*? 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=20041117225921.GA22472@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).