From: David Carlton <carlton@math.stanford.edu>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Outstanding?
Date: Fri, 27 Sep 2002 09:40:00 -0000 [thread overview]
Message-ID: <ro13crvmlmw.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3D93CD83.5020704@redhat.com>
On Thu, 26 Sep 2002 23:16:19 -0400, Andrew Cagney <ac131313@redhat.com> said:
> My pending / sep mail boxes contain the attached. If you see
> something that has been resolved, let me know.
I think I've gone through and spotted all the ones that are my fault
(though, given their number, I probably missed some). If I'm grouping
messages together, they all refer to the same thing, so if I say "This
has been taken care of" it refers to all the messages right above it.
Basically, there's only one issue of mine that's open right now.
> DWARF-2, static data members
> [David Carlton <carlton@math.Stanford.EDU>] [RFA] DWARF-2, static
> data members
> [RFA] DWARF-2, static data members
This is still outstanding. It's the only thing here that is
outstanding; I think the patch is pretty obvious and I would prefer to
get it in before 5.3, if possible, but it's not a critical situation.
(Basicaly, GCC and GDB both make the same mistake, so everything works
fine now.)
> [David Carlton <carlton@math.Stanford.EDU>] Re: [RFA] dwarf2read.c:
I'm not sure what this is, so I wouldn't worry about it: it's
doubtless the same as one of the other messages cited.
> [David Carlton <carlton@math.Stanford.EDU>] Re: [RFA] dwarf2read.c: set TYPE_DOMAIN_TYPE correctly for methods
> [David Carlton <carlton@math.Stanford.EDU>] [RFA] dwarf2read.c: set TYPE_DOMAIN_TYPE correctly for methods
> [RFA] dwarf2read.c: set TYPE_DOMAIN_TYPE correctly for methods
This has been taken care of.
> [Fwd: superfluous line in hpread.c]
> superfluous line in hpread.c
This has been taken care of.
> dwarf2_build_psymtabs should check that .debug_line exists
This has been taken care of.
> [RFA] convert blocks to dictionaries, phase 1, main part
> [RFA] convert blocks to dictionaries, phase 1, mdebugread.c
> [RFC] environment.c
> adding namespace support to GDB
This is being pulled back and reworked.
> [RFA] delete BLOCK_SHOULD_SORT
Jim Blandy has responded to it, and right now it's on hold while
issues he raised get worked out. (It's not a bug, so there's
certainly no reason to worry about it before 5.3 gets released.)
> [rfa/c++-testsuite]: printing out methods
> [rfa/c++testsuite] (was Re: patch for PR gdb/574)
> [rfa/c++testsuite] (was patch for PR gdb/574)
> [rfa/testsuite] more tests in gdb.c++/m-static
These have been taken care of.
> fix for gdb/635
> references to uninitialized static const members
This has been taken care of.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-09-27 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 20:16 Outstanding? Andrew Cagney
2002-09-27 7:24 ` Outstanding? Daniel Jacobowitz
2002-09-27 9:26 ` Outstanding? Andrew Cagney
2002-09-27 9:40 ` David Carlton [this message]
2002-09-27 10:56 ` Outstanding? Andrew Cagney
2002-09-27 16:11 ` Outstanding? Jim Blandy
2002-09-27 16:22 ` Outstanding? David Carlton
2002-10-01 15:22 ` Outstanding? Michael Snyder
2002-10-01 16:20 ` Outstanding? Andrew Cagney
2002-10-01 17:38 ` Outstanding? Daniel Jacobowitz
2002-10-01 18:11 ` Outstanding? Andrew Cagney
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=ro13crvmlmw.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@redhat.com \
--cc=gdb-patches@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