On Jul 13, 2007, at 6:57 PM, Joseph Wakeling wrote:
Benoit SIGOURE wrote:
Hmm you are right, I didn't notice during my test that I also had
zeros.
Build a static version of your project and it'll work.
./configure --disable-shared
make clean all CFLAGS='-pg -all-static'
Ahh, brilliant! Th
Benoit SIGOURE wrote:
> Hmm you are right, I didn't notice during my test that I also had zeros.
> Build a static version of your project and it'll work.
>
> ./configure --disable-shared
> make clean all CFLAGS='-pg -all-static'
Ahh, brilliant! Thank you ever so much.
The -all-static option gen
Bob Friesenhahn wrote:
> The profiling support might not be thread safe. While it may seem
> counter-productive to program tuning, it is usually recommended to use
> limited optimization, or no optimization at all.
I have an option for my program to use no threads and the same results
were produc
On Jul 13, 2007, at 5:36 PM, Joseph Wakeling wrote:
Benoit SIGOURE wrote:
The .la file is a piece of shell script that contains information
useful
to libtool.
Now the answer to your question is to ask libtool to run gprof (or
gdb)
for you:
./libtool --mode=execute gprof ./foo
Ah! That e
On Fri, 13 Jul 2007, Joseph Wakeling wrote:
Adding -pg to LDFLAGS doesn't help although I think you were right that
previously it was not being passed to the linker. The code is threaded
and I don't know if that might affect things.
The profiling support might not be thread safe. While it ma
Bob Friesenhahn wrote:
> It is important to know that profiling is based on both adding special
> code to functions during compilation (influenced by CFLAGS), and use of
> a special startup-module for linking. That means you should add -pg to
> LDFLAGS as well. Profiling will be easiest to deal w
On Jul 13, 2007, at 5:50 PM, Bob Friesenhahn wrote:
On Fri, 13 Jul 2007, Joseph Wakeling wrote:
I don't know whether I need to do more than add -pg to the CFLAGS
when
building the library or whether it's simply gprof I'm not using
correctly.
It is important to know that profiling is base
On Fri, 13 Jul 2007, Joseph Wakeling wrote:
I don't know whether I need to do more than add -pg to the CFLAGS when
building the library or whether it's simply gprof I'm not using correctly.
It is important to know that profiling is based on both adding special
code to functions during compila
Benoit SIGOURE wrote:
> The .la file is a piece of shell script that contains information useful
> to libtool.
>
> Now the answer to your question is to ask libtool to run gprof (or gdb)
> for you:
> ./libtool --mode=execute gprof ./foo
Ah! That explains much. Thank you.
I still get results tha
On Jul 13, 2007, at 4:39 PM, Joseph Wakeling wrote:
I have a small library which is built using the GNU autotools. It
also
includes some executable programs which use the main library. I would
like to profile the performance using gprof or another tool but have
been having trouble working ou
I have a small library which is built using the GNU autotools. It also
includes some executable programs which use the main library. I would
like to profile the performance using gprof or another tool but have
been having trouble working out how to do so. I tried simply adding -p
to the CFLAGS b
11 matches
Mail list logo
