From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/16726] RFE: provide a way to retrieve tapset function types
Date: Thu, 20 Mar 2014 19:55:00 -0000 [thread overview]
Message-ID: <bug-16726-6586-Rym4sLuxQa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16726-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16726
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jistone at redhat dot com
--- Comment #1 from Josh Stone <jistone at redhat dot com> ---
We shouldn't add type resolution to -vp1, but I think we could provide a
specialized option like --dump-functions that reports them all. This could run
through a few passes of type resolution too, but that still might not resolve
everything. I expect most types will be inferable by the function body, but
there could be some that depend on how the user calls it. Leaving those listed
ambiguously is probably correct.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-03-20 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 20:21 [Bug tapsets/16726] New: " aferrazz at redhat dot com
2014-03-20 19:55 ` jistone at redhat dot com [this message]
2014-03-21 18:39 ` [Bug tapsets/16726] " jlebon at redhat dot com
2014-04-01 19:53 ` jlebon at redhat dot com
2014-04-01 19:53 ` jlebon at redhat dot com
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=bug-16726-6586-Rym4sLuxQa@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).