From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] c++/12266 (again) [cp_demangled_name_parse_free-4.patch]
Date: Sat, 13 Aug 2011 16:51:00 -0000 [thread overview]
Message-ID: <20110813165113.GB2217@host1.jankratochvil.net> (raw)
In-Reply-To: <4E419712.3070709@redhat.com>
On Tue, 09 Aug 2011 22:22:42 +0200, Keith Seitz wrote:
> ChangeLog
> 2011-08-09 Keith Seitz <keiths@redhat.com>
>
> * cp-name-parser.y (struct demangle_info): Remove unused
> member PREV.
> (d_grab): Likewise.
> (allocate_info): Change return type to struct demangle_info *.
> Always allocate a new demangle_info.
> Remove unused PREV pointer.
> (cp_new_demangle_parse_info): New function.
> (cp_demangled_name_parse_free): New function.
> (do_demangled_name_parse_free_cleanup): New function.
> (make_cleanup_cp_demangled_name_parse_free): New function.
> (cp_demangled_name_to_comp): Change return type to
> struct demangle_parse_info *.
> Allocate a new storage for each call.
> (main): Update usage for cp_demangled_name_to_comp
> API change.
> * cp-support.h (struct demangle_parse_info): New structure.
> (cp_demangled_name_to_comp): Update API change for
> return type.
> (cp_new_demangle_parse_info): Declare.
> (make_cleanup_cp_demangled_name_parse_free): New declaration.
> (cp_demangled_name_parse_free): Declare.
> * cp-support.c (cp_canonicalize_string): Update API
> change for cp_demangled_name_to_comp.
> (mangled_name_to_comp): Likewise.
> Return struct demangle_parse_info, too.
> (cp_class_name_from_physname): Update mangled_name_to_comp
> API change.
> (method_name_from_physname): Likewise.
> (cp_func_name): Update API change for cp_demangled_name_to_comp.
> (cp_remove_params): Likewise.
> * python/py-type.c (typy_legacy_template_argument): Likewise.
I find it OK now.
Thanks,
Jan
next prev parent reply other threads:[~2011-08-13 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 13:16 [RFA] c++/12266 (again) Keith Seitz
2011-08-01 20:38 ` Tom Tromey
2011-08-02 16:08 ` Tom Tromey
2011-08-02 17:58 ` Keith Seitz
2011-08-02 20:28 ` [RFA] c++/12266 (again) [cp_demangled_name_parse_free-4.patch] Jan Kratochvil
2011-08-09 20:23 ` Keith Seitz
2011-08-13 16:51 ` Jan Kratochvil [this message]
2011-08-18 16:22 ` Keith Seitz
2011-08-02 20:37 ` [RFA] c++/12266 (again) [cp_canonicalize_no_typedefs-4.patch] Jan Kratochvil
2011-08-09 20:48 ` Keith Seitz
2011-08-13 16:50 ` Jan Kratochvil
2011-08-18 16:25 ` Keith Seitz
2011-08-18 16:35 ` 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=20110813165113.GB2217@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.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