From: Nick Clifton <nickc@redhat.com>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
binutils@sourceware.org
Subject: Re: [PATCH V4] gprofng: a new GNU profiler
Date: Fri, 10 Dec 2021 09:38:25 +0000 [thread overview]
Message-ID: <44e0ca3c-0792-7fc2-bff4-0918f1f4bea2@redhat.com> (raw)
In-Reply-To: <7dadb881-ab4b-de4a-0453-6d8661a8cd83@oracle.com>
Hi Vladimir,
> For x86_64/i686, gprofng should be built twice to support profiling for
> both 32-bit and 64-bit applications:
> PREFIX=<YOUR_INSTALL_DIR>
> configure --enable-shared --prefix=$PREFIX --libdir=$PREFIX/lib64 && make && make install
> configure --enable-shared --prefix=$PREFIX CC='gcc -m32' CXX='g++ -m32' \
> --target=i686-pc-linux-gnu --disable-gprofng-tools && make && make install
>
> For ARM:
> configure --enable-shared --prefix=$PREFIX && make install
Am I correct in thinking that gprofng only supports x86/x86_64 and ARM ?
To me this is a concern as the intention of the binutils project is to
support as wide a range of architectures as possible.
Is it simple to add other architectures ? What work needs to be done ?
Cheers
Nick
next prev parent reply other threads:[~2021-12-10 9:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fcc77804-0d0c-0f8e-5c3b-3ac034340b1a@oracle.com>
2021-11-03 18:05 ` Vladimir Mezentsev
2021-11-15 18:13 ` Ping: " Vladimir Mezentsev
2021-11-29 17:34 ` Vladimir Mezentsev
2021-12-10 9:38 ` Nick Clifton [this message]
2021-12-10 17:31 ` Vladimir Mezentsev
2021-12-13 15:13 ` Nick Clifton
2021-12-16 22:22 ` Vladimir Mezentsev
2022-01-12 0:48 ` Vladimir Mezentsev
2022-01-12 12:42 ` Nick Clifton
2022-01-12 15:17 ` Jose E. Marchesi
2022-01-12 15:23 ` Jose E. Marchesi
[not found] ` <c26c71b2-8cf1-2eef-206f-14c4774b2ba0@oracle.com>
2022-01-26 12:04 ` Nick Clifton
2022-01-26 17:10 ` Vladimir Mezentsev
2022-01-27 14:34 ` Jose E. Marchesi
2022-02-02 12:40 ` Maciej W. Rozycki
2022-02-02 16:30 ` Jose E. Marchesi
2022-02-03 6:23 ` Vladimir Mezentsev
2022-02-03 11:02 ` Maciej W. Rozycki
2022-02-03 12:16 ` Jose E. Marchesi
2022-03-02 19:47 ` Vladimir Mezentsev
2022-03-04 13:53 ` Nick Clifton
2022-03-07 21:42 ` Vladimir Mezentsev
2022-03-07 21:57 ` H.J. Lu
2022-03-07 22:25 ` Vladimir Mezentsev
2022-03-09 16:36 ` Nick Clifton
2022-03-09 21:13 ` Vladimir Mezentsev
2022-03-14 11:12 ` Martin Liška
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=44e0ca3c-0792-7fc2-bff4-0918f1f4bea2@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=vladimir.mezentsev@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).