Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190408122120.GR23599@brightrain.aerifal.cx>
Date: Mon, 8 Apr 2019 08:21:20 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Profiling musl

On Mon, Apr 08, 2019 at 12:15:04PM +0200, Pascal Felber wrote:
> Dear all,
> 
> Does anyone have experience with profiling musl? We are running into
> performance issues (after modifying some of the musl code) and would
> like to understand where the overheads come from, but profiling with
> gprof does not work and we have issues with valgrind. Any help will
> be greatly appreciated.

I would use perf(1). Making gprof work has been a very low priority
(and maybe non-starter if the stuff needed for support would be
invasive) since its model inherently perturbs the performance
properties of the code badly.

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.