From: "Markus Schöpflin" <no.spam@spam.spam>
Subject: Re: Profiling Ada binaries
Date: Mon, 25 Jul 2016 09:01:05 +0200
Date: 2016-07-25T09:01:05+02:00 [thread overview]
Message-ID: <nn4dfh$1cog$1@gioia.aioe.org> (raw)
In-Reply-To: nmtcns$81a$1@dont-email.me
Am 22.07.2016 um 17:05 schrieb Alejandro R. Mosteo:
> Incidentally, you might want to try with callgrind / kcachegrind to compare
> results. IIRC gprof is less accurate given that it instruments code with some
> granularity while valgrind does not have that limitation.
We tried that before, but *grind slows down performance too much, so we cannot
profile the affected binary. (It's some kind of soft real time application, so
we can't just let it sit and run over night.)
It currently looks like we have some success with perf right now. The key
seems to be to add "-fno-inline-functions-called-once" to the compilation
flags to get any meaningful call stack.
Markus
next prev parent reply other threads:[~2016-07-25 7:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 13:24 Profiling Ada binaries Markus Schöpflin
2016-07-22 14:59 ` Alejandro R. Mosteo
2016-07-22 15:05 ` Alejandro R. Mosteo
2016-07-25 7:01 ` Markus Schöpflin [this message]
2016-07-25 16:45 ` rieachus
2016-07-25 17:14 ` Simon Wright
2016-07-25 22:05 ` rieachus
2016-07-26 8:37 ` Markus Schöpflin
2016-08-01 22:40 ` rieachus
2016-08-01 23:36 ` Jeffrey R. Carter
2016-08-02 7:00 ` Markus Schöpflin
2016-08-05 3:18 ` rieachus
2016-08-05 20:27 ` Randy Brukardt
2016-08-02 6:39 ` Markus Schöpflin
2016-07-25 6:57 ` Markus Schöpflin
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox