From: Rakesh Pandit <rakesh.pandit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Arnaldo Carvalho de Melo
<acme-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
Cc: dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: option for printing all matching function names
Date: Wed, 5 May 2010 20:00:28 +0530 [thread overview]
Message-ID: <y2rb401d2531005050730q130526f0o7fa0950958e3ad92@mail.gmail.com> (raw)
In-Reply-To: <20100505131230.GA10363-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
On 5 May 2010 18:42, Arnaldo Carvalho de Melo wrote:
> Em Wed, May 05, 2010 at 09:44:01AM -0300, Arnaldo Carvalho de Melo escreveu:
[..]
> https://bugzilla.redhat.com/show_bug.cgi?id=495606
>
> <quote>
> Actually this does not results in correct match because corresponding
> symbool name which we provide it with function arg is mangled. In case
> we want to get a perfect matched we need to provide it de-mangled actual
> function name.
>
> But for C++ say (even in C) we can have more then one function with same
> name. In that case right now it will just print the first match.
> </quote>
>
> So what you want is that we traverse all the C++ classes finding which
> ones have methods with that name, which is way more sensible than what
> pfunct, being mostly oriented, so far, to C, does.
>
> I don't have time right now to devote to this, but what you want is to:
>
No problem, I will try to get some patches for review ready.
> 1. go on CU by CU looking at all structs
> 2. look at each namespace in them looking for functions with the desired
> name, printing it in some C++ sensible way, perhaps:
>
> return_type1 class_foo::method_searched(parameter list1); /* mangled name=EQWTVARSAE */
> return_type2 class_foo::method_searched(parameter list2); /* mangled name=YTEYRWTQRD */
>
> etc.
>
> What I suggested about --all-units still is useful as we can have the
> functions with the same name in multiple object files in C too, they
> just have to be static not to cause linking problems.
>
Exactly,
I would consider it as a two step problem. First add --all-units which
works as you specified in previous reply. Later on work on what you
suggested in here (on giving output somewhat more sensible C++ way),
following the very algo you mentioned.
I will first work on former first (--all-units) and then later move to C++ :)
Between thanks for your suggestions.
Regards,
--
Rakesh Pandit
https://fedoraproject.org/wiki/User:Rakesh
freedom, friends, features, first
--
To unsubscribe from this list: send the line "unsubscribe dwarves" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-05-05 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 11:45 option for printing all matching function names Rakesh Pandit
[not found] ` <q2qb401d2531005050445wb33461ecnab0f752909fb4a4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-05 12:44 ` Arnaldo Carvalho de Melo
[not found] ` <20100505124401.GG970-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2010-05-05 13:12 ` Arnaldo Carvalho de Melo
[not found] ` <20100505131230.GA10363-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2010-05-05 14:30 ` Rakesh Pandit [this message]
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=y2rb401d2531005050730q130526f0o7fa0950958e3ad92@mail.gmail.com \
--to=rakesh.pandit-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=acme-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org \
--cc=dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 NNTP newsgroup(s).