From: David Carlton <carlton@math.stanford.edu>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com, Jim Blandy <jimb@redhat.com>
Subject: Re: PING [RFA] DWARF-2, static data members
Date: Thu, 05 Dec 2002 16:16:00 -0000 [thread overview]
Message-ID: <ro1u1hs10ty.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <15855.58328.854004.977049@localhost.redhat.com>
On Thu, 5 Dec 2002 18:40:08 -0500, Elena Zannoni <ezannoni@redhat.com> said:
> David Carlton writes:
>> On Thu, 5 Dec 2002 15:24:10 -0500, Elena Zannoni <ezannoni@redhat.com> said:
>>> 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.
That's a good point. If my patch had made it into 5.3, then I'd be
tempted to send it to the GCC folks now, but 5.3 has been frozen so
that didn't happen. I don't have enough experience with how GDB's and
GCC's release cycles work to know when it's best to submit it to GCC,
but I'm pretty leery about doing so until I have a good idea as to
when my patch will make it into a released version of GDB.
Especially since the matter at hand really is pretty unimportant, so
I don't think there's much reason to try to optimize the process in
this situation.
> 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
Yeah, so I heard. So matters are progressing nicely on that front.
David Carlton
carlton@math.stanford.edu
prev parent reply other threads:[~2002-12-05 23:51 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
2002-12-05 16:16 ` David Carlton [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=ro1u1hs10ty.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ezannoni@redhat.com \
--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