Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Elena Zannoni <ezannoni@redhat.com>,
	gdb-patches@sources.redhat.com, Jim Blandy <jimb@redhat.com>
Subject: Re: PING [RFA] DWARF-2, static data members
Date: Thu, 05 Dec 2002 15:45:00 -0000	[thread overview]
Message-ID: <15855.58328.854004.977049@localhost.redhat.com> (raw)
In-Reply-To: <ro1fztc2ilq.fsf@jackfruit.Stanford.EDU>

David Carlton writes:
 > On Thu, 5 Dec 2002 15:24:10 -0500, Elena Zannoni <ezannoni@redhat.com> said:
 > 
 > > Makes sense. Hoever, could you leave the comments inside the 'then' bodies?
 > > Like 
 > > if (blah)
 > > {
 > >  /* C++ static member.  */
 > >  [...]
 > > }
 > 
 > Will do.
 > 
 > > I think it would be useful to add a g++ version number or a date in
 > > the comments, because at some point down the road we may want to
 > > obsolete the old form.
 > 
 > Right, I'll add that.
 > 
 > > Was the patch to gcc submitted, or the gcc PR fixed otherwise?
 > 
 > No, I can't submit the patch to GCC until a version of GDB including
 > this patch is released, because otherwise they'll emit debugging info
 > that we can't handle.
 > 

I know, but I figured that, given their 'freeze' cycles, it could
get reviewed in the meantime.

Speaking of which, I've heard rumours that the Dberlin patch for
namespace debug info has been reviewed... Indeed it has:
http://gcc.gnu.org/ml/gcc-patches/2002-11/msg00978.html

Elena

 > I'll commit it with the changes to the comments that you requested.
 > 
 > David Carlton
 > carlton@math.stanford.edu


  reply	other threads:[~2002-12-05 23:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 17:04 David Carlton
2002-12-05 12:28 ` Elena Zannoni
2002-12-05 14:44   ` David Carlton
2002-12-05 15:45     ` Elena Zannoni [this message]
2002-12-05 16:16       ` David Carlton

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=15855.58328.854004.977049@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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