[Ecls-list] ECL shootout

[Gabriel Dos Reis]

On Fri, Jul 3, 2009 at 2:18 AM, Juan Jose
Garcia-Ripoll<juanjose.garciaripoll at googlemail.com> wrote:
> On Fri, Jul 3, 2009 at 9:06 AM, Gabriel Dos
> Reis<gdr at integrable-solutions.net> wrote:
>> Sorry I was unclear: I do expect that on those platforms such as
>> OSX, you would continue to do as before.  It only on platforms
>> such as linux, and I suspect *BSD that shared libraries are not
>> profiled correctly.
>
> Is it really the case that profiled libraries are impossible? Can it
> be just that we make a mistake when installing ECL, such as stripping
> it? I seem to recall *_p.so libraries sitting around in my old Linux
> box.

OK.  First, a confession.  My recollection of "gprof" not working
with a shared library goes back to 1999-2001 era when I was
doing some profiling work for the GNU implementation libstdc++.
And it turned out that, well, gprof was not up to the job.
Then, I tried the build yesterday (thinking that the situation
had improved, based on your  hinting that it might work).  But, things
did not improve.  At least not with gprof.

I just did a search and hit this message

   http://sourceware.org/ml/binutils/2007-04/msg00248.html

and Dan's reply

    http://sourceware.org/ml/binutils/2007-04/msg00250.html

suggests 'sprof' or 'oprofile'.  'oprofile' is not an option.
So, I'll try 'sprof'.


In any case, I think the manual of ECL should include some
discussion about how to make --with-profile-cflags most effective,
e.g. suggesting profilers, etc.

-- Gaby