From: Tom Tromey <tromey@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Perform a namespace lookup at every block level
Date: Mon, 21 Dec 2009 21:55:00 -0000 [thread overview]
Message-ID: <m3skb4801p.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B0C3011.4080000@redhat.com> (Sami Wagiaalla's message of "Tue, 24 Nov 2009 14:12:17 -0500")
>>>>> "Sami" == Sami Wagiaalla <swagiaal@redhat.com> writes:
Sami> Updating patch because of changes in patch 1/2
Sami> 2009-11-16 Sami Wagiaalla <swagiaal@redhat.com>
Sami> * cp-namespace.c (cp_lookup_symbol_namespace): Added
Sami> search_parent argument.
Sami> (cp_add_using): Initialize 'searched' field.
Sami> (cp_copy_usings): Copy searched field.
Sami> * cp-support.h: Add 'searched' field to using_direct struct.
Sami> (cp_lookup_symbol_imports): Ditto.
Sami> * cp-namespace.c (cp_lookup_symbol_imports): Ditto.
Sami> Perform recursive search.
Sami> Implement non parent search.
Sami> * valops.c (value_maybe_namespace_elt): Updated.
This is nearly ok.
Note that the patch got a little mangled, and this resubmission was
missing the changes in testsuite/.
Sami> 2009-11-16 Sami Wagiaalla <swagiaal@redhat.com>
Sami> * gdb.cp/namespace-stress.exp: New test.
Sami> * gdb.cp/namespace-stress.cc: New test program.
Sami> * gdb.cp/namespace-recursive.exp: New test.
Sami> * gdb.cp/namespace-recursive.cc: New test program.
Sami> * gdb.cp/namespace-stress.exp: New test.
Sami> * gdb.cp/namespace-stress.cc: New test program.
We're mostly following 8.3 rules, so I would suggest renaming these to
"ns-*".
Also, in an archer fix you had namespace-stress-declaration... what
happened to that? The corresponding code patch seems to include
reset_directive_searched:
http://sourceware.org/ml/archer-commits/2009-q4/msg00094.html
Speaking of which, reset_directive_searched is not mentioned in the
ChangeLog.
Tom
next prev parent reply other threads:[~2009-12-21 21:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 15:10 [patch] " Sami Wagiaalla
2009-07-10 20:16 ` Daniel Jacobowitz
2009-07-13 17:55 ` Sami Wagiaalla
2009-07-23 19:46 ` Sami Wagiaalla
2009-07-23 22:19 ` Sami Wagiaalla
2009-07-29 22:12 ` Tom Tromey
2009-08-18 20:34 ` [patch 1/2] " Sami Wagiaalla
2009-10-13 19:47 ` Tom Tromey
2009-10-20 20:50 ` Sami Wagiaalla
2009-11-10 22:23 ` Tom Tromey
2009-11-10 22:26 ` Tom Tromey
2009-11-16 15:32 ` Sami Wagiaalla
2009-11-16 19:16 ` Sami Wagiaalla
2009-11-24 19:06 ` Sami Wagiaalla
2009-12-21 21:44 ` Tom Tromey
2009-08-18 20:46 ` [patch 2/2] " Sami Wagiaalla
2009-09-04 16:57 ` Sami Wagiaalla
2009-10-13 20:22 ` Tom Tromey
2009-10-22 17:47 ` Sami Wagiaalla
2009-11-10 22:52 ` Tom Tromey
2009-11-16 17:55 ` Sami Wagiaalla
2009-11-24 19:12 ` Sami Wagiaalla
2009-12-21 21:55 ` Tom Tromey [this message]
2010-01-11 21:24 ` Sami Wagiaalla
2010-01-12 17:43 ` Tom Tromey
2010-01-14 16:47 ` Sami Wagiaalla
2010-01-14 20:18 ` Sami Wagiaalla
2010-01-15 18:06 ` Tom Tromey
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=m3skb4801p.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=swagiaal@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