From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: Thomas Gruber <Thomas.Gruber@fau.de>, binutils@sourceware.org
Subject: Re: [gprofng] Parsing of function definitions fails
Date: Mon, 21 Mar 2022 10:51:53 -0700 [thread overview]
Message-ID: <a6afda7d-9cb4-8a3b-f3ba-0851786fbfba@oracle.com> (raw)
In-Reply-To: <27f1cab3-237b-2c9c-f202-4e2b8c26fa3f@fau.de>
On 3/21/22 09:17, Thomas Gruber wrote:
> Hi,
>
> A colleague of mine reported problems when specifying C++ functions in
> gp-display-text:
>
> # the function 'csr_spmv_kernel<double, int>' exists
>
> (gp-display-text) fsingle csr_spmv_kernel<double, int>
Hi Thomas,
This demangled name should t be surrounded by double quotes:
fsingle "csr_spmv_kernel<double,int>(long,long,int const*,int
const*,double const*,double const*,double*) "
Or you can use this form:
fsingle csr_spmv_kernel [N]
If N is absent, gp-display-text asks which function you want to see.
Thank you,
-Vladimir
> Error: Invalid number entered: int>
> Error: Invalid number entered: int>
> Error: No function with given name `csr_spmv_kernel<double,' found.
> (gp-display-text) fsingle csr_spmv_kernel<double,int>
> Error: No function with given name `csr_spmv_kernel<double,int>' found.
>
> So, spaces in the template parameter list seem to be bad. Moreover,
> '*' in the function parameter list seem to be not parsed properly:
>
> (gp-display-text) source csr_spmv_kernel<double,int>(long,long,int
> const*,int const*,double const*,double const*,double*)
> Warning: extra arguments to source command, line 2
> Error: Invalid number entered: const*,int
> Error: Invalid number entered: const*,int
> Error: No function or file with given name
> `csr_spmv_kernel<double,int>(long,long,int' found.
>
>
> Best,
> Thomas
>
>
next prev parent reply other threads:[~2022-03-21 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 16:17 Thomas Gruber
2022-03-21 17:51 ` Vladimir Mezentsev [this message]
2022-03-22 16:51 ` Thomas Gruber
2022-03-22 18:46 ` Vladimir Mezentsev
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=a6afda7d-9cb4-8a3b-f3ba-0851786fbfba@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=Thomas.Gruber@fau.de \
--cc=binutils@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).