public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/18141] massive perf issue trying to lookup namespaces in STRUCT_DOMAIN with gdb_index
Date: Mon, 30 Mar 2015 23:52:00 -0000	[thread overview]
Message-ID: <bug-18141-4717-qQ9cQ6UFin@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18141-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18141

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Doug Evans <devans@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=13ce92227425999aa2666f4d55286193df7d09ca

commit 13ce92227425999aa2666f4d55286193df7d09ca
Author: Doug Evans <dje@google.com>
Date:   Mon Mar 30 16:41:05 2015 -0700

    PR c++/18141

    gdb/ChangeLog:

        PR c++/18141
        * cp-namespace.c (cp_search_static_and_baseclasses): Always look for
        klass in VAR_DOMAIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-03-30 23:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 19:26 [Bug c++/18141] New: " dje at google dot com
2015-03-18 19:29 ` [Bug c++/18141] " dje at google dot com
2015-03-30 23:52 ` cvs-commit at gcc dot gnu.org [this message]
2015-03-31 22:59 ` dje at google dot com
2015-05-12 21:14 ` dje at google dot com
2015-05-12 21:17 ` dje at google dot com
2015-05-15 19:47 ` dje at google dot com
2015-05-27  0:22 ` cvs-commit at gcc dot gnu.org
2015-05-27  0:25 ` dje at google dot com

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=bug-18141-4717-qQ9cQ6UFin@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).