unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: Anyone know how to compile with profiling when using libtool?
Date: Sat, 15 Mar 2003 07:29:05 +1000	[thread overview]
Message-ID: <87vfylvdr2.fsf@zip.com.au> (raw)
In-Reply-To: <87adg0jdwx.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Wed, 12 Mar 2003 18:41:50 -0600")

Rob Browning <rlb@defaultvalue.org> writes:
>
> Though I can augment CFLAGS so that each .c file is compiled with -g
> -pg, I haven't figured out a way to keep libtool from removing -pg
> from the link line.  It seems like libtool is removing -pg (and
> -no-undefined, etc.) from the gcc command line just before issuing the
> link command.

One workaround is to make a script "my-gcc-pg" which just execs gcc
-pg, and use that by configuring with CC=my-gcc-pg.  I think libtool
recognises gcc based on preprocessor defines, so the name of the
script hopefully doesn't matter.

To do it directly with libtool you can insinuate -Wc,-pg into the
flags, by overriding LDFLAGS or guile_LDFLAGS or whatever.

> If at all possible, I'd rather not have it second guess me for at
> least some of the options...

Rumour has it the next libtool will leave alone anything it doesn't
recognise.


Incidentally, http://sourceforge.net/projects/fnccheck is quite a nice
profiler, based on gcc -finstrument-functions.  It uses the i586 rdtsc
to record function entry and exit, so it's a lot more accurate than
10ms sampling by prof.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2003-03-14 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13  0:41 Anyone know how to compile with profiling when using libtool? Rob Browning
2003-03-14 21:29 ` Kevin Ryde [this message]

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vfylvdr2.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).