Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfa] Stabs documentation tweak for pointers to members
Date: Wed, 02 Aug 2006 21:02:00 -0000	[thread overview]
Message-ID: <20060802210158.GA31053@nevyn.them.org> (raw)
In-Reply-To: <200608022059.k72KxQNG007451@elgar.sibelius.xs4all.nl>

On Wed, Aug 02, 2006 at 10:59:26PM +0200, Mark Kettenis wrote:
> > Date: Tue, 1 Aug 2006 23:26:55 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > When working on pointers to members I encountered only one place in
> > GDB that seemed to need an actual "member" type, instead of just "pointer to
> > member" (which is not really a pointer at all).  That was in the stabs
> > reader.  The documentation says that stabs has a "member" construct, and
> > represents pointers to members as pointers to that construct.  The reader
> > code matches this.
> > 
> > But if this was ever the case for GCC, it hasn't been for a while.  Now
> > the @ descriptor means pointer to member.  This patch corrects the manual;
> > the final patch will correct the stabs reader.
> 
> For what it is worth, I couldn't find any refernce to @@ in the Sun
> "Stabs Interface Manual", so it's indeed very likely this is a gcc
> invention.

Yes, that's correct.  The Sun manual documents a different solution to
this problem, starting with 'Y' (I think it's 'YM').  The two
"standards" diverged when there was no C++ support in Sun's; I suspect
GCC got C++ first, but Sun got it better.  But I don't actually know
any of the history here so I'm just guessing.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-08-02 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02  3:26 Daniel Jacobowitz
2006-08-02  3:30 ` Eli Zaretskii
2006-08-02  3:31   ` Daniel Jacobowitz
2006-08-02 21:00 ` Mark Kettenis
2006-08-02 21:02   ` Daniel Jacobowitz [this message]

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=20060802210158.GA31053@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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