From: Doug Evans <dje@google.com>
To: Keith Seitz <keiths@redhat.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFA/7.8 blocker] Revert c++/16253
Date: Fri, 06 Jun 2014 21:20:00 -0000 [thread overview]
Message-ID: <CADPb22RhUsbtbKgfauZBj7fOV39D-=O4w0WLRo8o09KqiVas6w@mail.gmail.com> (raw)
In-Reply-To: <5390ABAA.2080209@redhat.com>
On Thu, Jun 5, 2014 at 10:40 AM, Keith Seitz <keiths@redhat.com> wrote:
> Hi,
>
> We decided to revert my earlier patch for c++/16253 (variable name/tag name
> collision) because Doug reports that it causes a sizable performance
> regression:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=16253
>
> This patch reverts the whole thing.
>
> Tested on Fedora 20, x86_64 and native-gdbserver.
>
> Keith
>
> ChangeLog
> 2014-06-05 Keith Seitz <keiths@redhat.com>
>
> Revert:
> PR c++/16253
> * ada-lang.c (ada_symbol_matches_domain): Moved here and renamed
> from symbol_matches_domain in symtab.c. All local callers
> of symbol_matches_domain updated.
> (standard_lookup): If DOMAIN is VAR_DOMAIN and no symbol is found,
> search STRUCT_DOMAIN.
> (ada_find_any_type_symbol): Do not search STRUCT_DOMAIN
> independently. standard_lookup will do that automatically.
> * cp-namespace.c (cp_lookup_symbol_nonlocal): Explain when/why
> VAR_DOMAIN searches may return a STRUCT_DOMAIN match.
> (cp_lookup_symbol_in_namespace): Likewise.
> If no VAR_DOMAIN symbol is found, search STRUCT_DOMAIN.
> (cp_lookup_symbol_exports): Explain when/why VAR_DOMAIN searches
> may return a STRUCT_DOMAIN match.
> (lookup_symbol_file): Search for the class name in STRUCT_DOMAIN.
> * cp-support.c: Include language.h.
> (inspect_type): Explicitly search STRUCT_DOMAIN before searching
> VAR_DOMAIN.
> * psymtab.c (match_partial_symbol): Compare the requested
> domain with the symbol's domain directly.
> (lookup_partial_symbol): Likewise.
> * symtab.c (lookup_symbol_in_language): Explain when/why
> VAR_DOMAIN searches may return a STRUCT_DOMAIN match.
> If no VAR_DOMAIN symbol is found, search STRUCT_DOMAIN for
> appropriate languages.
> (symbol_matches_domain): Renamed `ada_symbol_matches_domain'
> and moved to ada-lang.c
> (lookup_block_symbol): Explain that this function only returns
> symbol matching the requested DOMAIN.
> Compare the requested domain with the symbol's domain directly.
> (iterate_over_symbols): Compare the requested domain with the
> symbol's domain directly.
> * symtab.h (symbol_matches_domain): Remove.
>
> testsuite/ChangeLog
> 2014-06-05 Keith Seitz <keiths@redhat.com>
>
> Revert:
> PR c++/16253
> * gdb.cp/var-tag.cc: New file.
> * gdb.cp/var-tag.exp: New file.
> * gdb.dwarf2/dw2-ada-ffffffff.exp: Set the language to C++.
> * gdb.dwarf2/dw2-anon-mptr.exp: Likewise.
> * gdb.dwarf2/dw2-double-set-die-type.exp: Likewise.
> * gdb.dwarf2/dw2-inheritance.exp: Likewise.
Thanks!
I've reverified my perf regression with HEAD, and then verified this
patch makes it go away.
[gotta love looking up "int64" 10 thousand times. 1/2 :-)]
next prev parent reply other threads:[~2014-06-06 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 17:41 Keith Seitz
2014-06-06 21:20 ` Doug Evans [this message]
2014-06-06 23:29 ` Doug Evans
2014-06-07 17:42 ` Keith Seitz
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='CADPb22RhUsbtbKgfauZBj7fOV39D-=O4w0WLRo8o09KqiVas6w@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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