Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb@sourceware.org
Subject: Re: cp-name-parser.y
Date: Fri, 29 Feb 2008 19:09:00 -0000	[thread overview]
Message-ID: <20080229185513.GA2793@caradoc.them.org> (raw)
In-Reply-To: <47C84D48.2020807@qnx.com>

On Fri, Feb 29, 2008 at 01:22:00PM -0500, Aleksandar Ristovski wrote:
> Hello,
>
> Is it just me or is cpname_parse really not being used at all? I see there 
> has been some effort put into parsing c++ specific sutff, but is it 
> unfinished, or what is going on?
>
> If you could, let me know how mature is that code there and can it be used.

What would you like to use it for?

It's not used yet for much.  I have a patch, most recently posted
around the end of October 2007, which uses it for every C++ symbol
we read in.  That's to fix symbol lookup issues for templates, and
so forth.  But the patch is a bit of a slowdown and I want to look at
your speedups first before I go there.  I'll be doing that soon.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-02-29 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 18:39 cp-name-parser.y Aleksandar Ristovski
2008-02-29 19:09 ` Daniel Jacobowitz [this message]
2008-02-29 19:32   ` cp-name-parser.y Aleksandar Ristovski
2008-02-29 19:49     ` cp-name-parser.y Daniel Jacobowitz
2008-02-29 20:15       ` cp-name-parser.y Aleksandar Ristovski
2008-02-29 21:49         ` cp-name-parser.y Daniel Jacobowitz
2008-03-03 17:02           ` cp-name-parser.y Aleksandar Ristovski
2008-03-03 17:22             ` Daniel Jacobowitz
2008-03-03 18:33               ` cp-name-parser.y Aleksandar Ristovski
2008-03-03 20:05                 ` cp-name-parser.y Daniel Jacobowitz

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=20080229185513.GA2793@caradoc.them.org \
    --to=drow@false.org \
    --cc=aristovski@qnx.com \
    --cc=gdb@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