Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: gdb@sources.redhat.com
Subject: [Fwd: Re: c++/1512: no canonical way to output names of C++ types]
Date: Thu, 15 Jan 2004 16:18:00 -0000	[thread overview]
Message-ID: <4006BD4E.4050007@gnu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 536 bytes --]

>  Fixes for this are in progress on drow-cplus-branch.  All the necessary
>  code is there, it just needs to be hooked up :)  I think I've gotten
>  derailed on some other problems first, though.  The basic problem is
>  that we want to canonicalize the names before adding them to the symbol
>  table, and that increases startup time.  I'm looking for ways to shave
>  startup time elsewhere.  I have a few ideas.

If it is going to be so expensive, can it be put off until later, when 
the canonical value is needed?

enjoy,
Andrew


[-- Attachment #2: Re: c++/1512: no canonical way to output names of C++ types --]
[-- Type: message/rfc822, Size: 3926 bytes --]

From: Daniel Jacobowitz <drow@mvista.com>
To: nobody@sources.redhat.com
Cc: gdb-prs@sources.redhat.com,
Subject: Re: c++/1512: no canonical way to output names of C++ types
Date: 14 Jan 2004 23:18:00 -0000
Message-ID: <20040114231800.3737.qmail@sources.redhat.com>

The following reply was made to PR c++/1512; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@mvista.com>
To: carlton@bactrian.org
Cc: gdb-gnats@sources.redhat.com
Subject: Re: c++/1512: no canonical way to output names of C++ types
Date: Wed, 14 Jan 2004 18:12:13 -0500

 On Wed, Jan 14, 2004 at 06:26:13PM -0000, carlton@bactrian.org wrote:
 > 
 > >Number:         1512
 > >Category:       c++
 > >Synopsis:       no canonical way to output names of C++ types
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          change-request
 > >Submitter-Id:   net
 > >Arrival-Date:   Wed Jan 14 18:28:00 UTC 2004
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     carlton@bactrian.org
 > >Release:        2004-01-14-cvs
 > >Organization:
 > >Environment:
 > any
 > >Description:
 > We currently don't have any canonical way to output
 > names of C++ types.  E.g. const char * vs.
 > char const *; more subtleties arise when dealing with
 > templates.
 > 
 > This is, of course, less important than the fact that
 > we don't know how to recognize different names
 > of types as equivalent when doing input, but it's
 > still unfortunate.
 
 Fixes for this are in progress on drow-cplus-branch.  All the necessary
 code is there, it just needs to be hooked up :)  I think I've gotten
 derailed on some other problems first, though.  The basic problem is
 that we want to canonicalize the names before adding them to the symbol
 table, and that increases startup time.  I'm looking for ways to shave
 startup time elsewhere.  I have a few ideas.
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer


             reply	other threads:[~2004-01-15 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 16:18 Andrew Cagney [this message]
2004-01-15 16:25 ` Daniel Jacobowitz
2004-01-15 16:33   ` Andrew Cagney
2004-01-15 16:47     ` 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=4006BD4E.4050007@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb@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