From: Arnaldo Carvalho de Melo <acme-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
To: Rakesh Pandit <rakesh.pandit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] pfunct: Introduced --all/-A
Date: Tue, 4 May 2010 13:18:03 -0300 [thread overview]
Message-ID: <20100504161803.GD970@ghostprotocols.net> (raw)
In-Reply-To: <l2nb401d2531005032356q9d0e569fh6f69d57e9f5784e6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Em Tue, May 04, 2010 at 12:26:52PM +0530, Rakesh Pandit escreveu:
> On 5 April 2010 13:01, Rakesh Pandit <rakesh.pandit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Hello,
> >
> > I have a request for enhancement (new option in pfunct) via which I
> > want pfunct to print signatures for all symbols in one go. To add to
> > it and as expected I want source code information per symbol if -l
> > option is specified.
> >
>
> ping for review ?
Isn't:
pfunct -V ~/bin/perf | grep \;$
equivalent?
Perhaps have a new flag to ask that no C comment like lines be issued?
so it would be:
pfunct -V --no-comments objfile
But ok, I'll add a '-P'/'--prototypes' option for that.
- Arnaldo
--
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
next prev parent reply other threads:[~2010-05-04 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 7:31 [PATCH] pfunct: Introduced --all/-A Rakesh Pandit
[not found] ` <g2wb401d2531004050031q14f3fb12y39f4e7b0316526c0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-04 6:56 ` Rakesh Pandit
[not found] ` <l2nb401d2531005032356q9d0e569fh6f69d57e9f5784e6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-04 16:18 ` Arnaldo Carvalho de Melo [this message]
[not found] ` <20100504161803.GD970-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2010-05-05 3:49 ` Rakesh Pandit
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=20100504161803.GD970@ghostprotocols.net \
--to=acme-f8uhvlngfzaxayomlchx1axock334eze@public.gmane.org \
--cc=dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rakesh.pandit-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.